Third Party Index

Snapshot 68555

Document
Status page
URL
https://status.specright.com/
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
83155 bytes
SHA-256 (raw)
7d1901427b0de5120e0bf242a0011e2481aeb3dc1a93d0a0367d546458b8e2fa
SHA-256 (normalized text)
9fea8e306f455dca242b8772320b2cfc0f6021e095a602a0d6cbdbe745a3447e

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Subscribe to UpdatesSubscribe
All Systems Operational
About This Site
Specright utilizes multiple layers (Hardware and Networking, Platform, and Application) to run the Specright Platform. The status of the servers and applications can be found in the following places:
For Salesforce Platform Status
Informational Notices
SALESFORCE LOGIN EXPERIENCE CHANGE — 2026
— — — — —
Email Becomes the Default Login Option — Sandbox rollout in progress; Production begins October 5, 2026
Salesforce is changing the default login experience on its standard login pages. Email address will replace username as the primary login prompt on login.salesforce.com and test.salesforce.com. Users who prefer to sign in with a username can still do so by selecting Log In with Username on the login page.
Sandboxes: Rollout began late August 2026; expected to complete by September 30, 2026
Production: Rollout begins October 5, 2026; majority complete in early November 2026
What is affected: This change applies only to browser (UI) logins on login.salesforce.com and test.salesforce.com. It does not apply to custom My Domain login pages, Experience Cloud login pages, SSO-initiated logins, or API and integration authentication. No Specright Platform functionality, data, or org configuration is changing as a result.
What your users will see: The login page will prompt for an email address first. If an email address is associated with more than one Salesforce account or org, users are presented with a selection screen to choose the org they want to enter. Registered passkeys continue to work with both the email and username login methods.
Recommended actions:
• Inform your users. Let your team know that the email prompt is expected and that Log In with Username remains available at any time.
• Review shared or unmonitored accounts. Email-based login requires access to the inbox for that address. Users who sign in with a shared alias or an unmonitored mailbox should sign in with a username instead.
• Update automated UI scripts and tests. If your team runs automated scripts that log in through the Salesforce UI, update them to click Log In with Username first, or navigate directly to the username screen by appending ?login=1 to the login URL (for example, https://login.salesforce.com/?login=1).
No action is required from Specright customers who access the platform through a custom My Domain URL or SSO. For questions, to confirm how your org is accessed, or for help updating integration or test scripts, please contact your Specright Customer Success contact or Specright Support. Full details are available in Salesforce's Prepare for Login Changes release note.
Uptime over the past 90 days. View historical uptime.
Specright Core Platform Operational
Specright API Services Operational
Specright R&D Workbench Operational
Informational Notices Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Oct 8, 2026
No incidents reported today.
Oct 7, 2026
No incidents reported.
Oct 6, 2026
No incidents reported.
Oct 5, 2026
No incidents reported.
Oct 4, 2026
No incidents reported.
Oct 3, 2026
No incidents reported.
Oct 2, 2026
No incidents reported.
Oct 1, 2026
No incidents reported.
Sep 30, 2026
No incidents reported.
Sep 29, 2026
No incidents reported.
Sep 28, 2026
No incidents reported.
Sep 27, 2026
No incidents reported.
Sep 26, 2026
No incidents reported.
Sep 25, 2026
No incidents reported.
Sep 24, 2026
No incidents reported.
Incident History Powered by Atlassian Statuspage