Sunshine 811 Outage History

Sunshine 811 is up right now

There were 10 Sunshine 811 outages since February 11, 2026 totaling 22h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sunshine811.com

Notice April 30, 2026

Desktop Authenticator Enrollment Degradation

Detected by Pingoru
Apr 30, 2026, 05:54 PM UTC
Resolved
Apr 30, 2026, 09:06 PM UTC
Duration
3h 11m
Timeline · 4 updates
  1. investigating Apr 30, 2026, 05:54 PM UTC

    We are currently addressing an issue impacting desktop authenticator enrollments .A subset of customers may experience intermittent delays or failures during desktop authenticator enrollment. Mitigation actions are in progress and are helping to reduce impact. Core authentication, SSO, and delivery services remain fully operational.

  2. investigating Apr 30, 2026, 05:57 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING]. Statuspage incident message [We are currently addressing an issue impacting desktop authenticator enrollments .A subset of customers may experience intermittent delays or failures during desktop authenticator enrollment. Mitigation actions are in progress and are helping to reduce impact. Core authentication, SSO, and delivery services remain fully operational.] has changed as [Mitigation actions have been implemented. The service has stabilized and recovery is underway. We will continue to monitor to ensure full resolution.]. " on alert: "Desktop Authenticator Enrollment Degradation"

  3. investigating Apr 30, 2026, 06:07 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED]. Statuspage incident message [Mitigation actions have been implemented. The service has stabilized and recovery is underway. We will continue to monitor to ensure full resolution.] has changed as [The issue has been resolved. Services have returned to normal operation, and customers should no longer experience delays or failures. We apologize for any inconvenience caused and thank you for your patience.]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. Statuspage incident component [Admin Panel] status [degraded_performance] has changed as [operational]. " on alert: "Desktop Authenticator Enrollment Degradation"

  4. resolved Apr 30, 2026, 09:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 27, 2026

Site Loading and Editing Issues

Detected by Pingoru
Apr 27, 2026, 04:09 PM UTC
Resolved
Apr 27, 2026, 05:25 PM UTC
Duration
1h 16m
Timeline · 4 updates
  1. investigating Apr 27, 2026, 04:09 PM UTC

    We are currently investigating issues with editing and loading sites.

  2. investigating Apr 27, 2026, 04:25 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident message [We are currently investigating issues with editing and loading sites.] has changed as [We are continuing to investigate this issue.]. " on alert: "Site Loading and Editing Issues"

  3. investigating Apr 27, 2026, 04:35 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING]. Statuspage incident message [We are continuing to investigate this issue.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Site Loading and Editing Issues"

  4. investigating Apr 27, 2026, 04:56 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [We are continuing to monitor for any further issues.]. " on alert: "Site Loading and Editing Issues"

Read the full incident report →

Notice April 18, 2026

SMS Delivery Failures

Detected by Pingoru
Apr 18, 2026, 04:30 AM UTC
Resolved
Apr 20, 2026, 03:31 PM UTC
Duration
2d 11h
Timeline · 3 updates
  1. investigating Apr 18, 2026, 04:30 AM UTC

    We are currently detecting an issue with carriers in the US region for SMS delivery. We are currently working with providers to restore the service. In the meantime, please use other means of authentication such as Duo Push.

  2. investigating Apr 18, 2026, 05:39 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident message [We are currently detecting an issue with carriers in the US region for SMS delivery. We are currently working with providers to restore the service. In the meantime, please use other means of authentication such as Duo Push.] has changed as [We are continuing to investigate the SMS delivery issue impacting all customers in the US region. Push notifications will continue to work as expected. Further updates will be provided as more information becomes available.]. " on alert: "SMS Delivery Failures"

  3. investigating Apr 18, 2026, 07:09 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [RESOLVED]. Statuspage incident message [We are continuing to investigate the SMS delivery issue impacting all customers in the US region. Push notifications will continue to work as expected. Further updates will be provided as more information becomes available.] has changed as [The SMS delivery issue impacting customers in the US region has been resolved. SMS passcode authentication is now functioning normally. We apologize for any inconvenience caused and thank you for your patience.]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. Statuspage incident component [SMS Message Delivery] status [partial_outage] has changed as [operational]. " on alert: "SMS Delivery Failures"

Read the full incident report →

Notice April 13, 2026

[StatusCake] Exactix - API status is Down

Detected by Pingoru
Apr 13, 2026, 06:39 PM UTC
Resolved
Apr 13, 2026, 06:40 PM UTC
Duration
39s
Timeline · 2 updates
  1. investigating Apr 13, 2026, 06:39 PM UTC

    Test Name: Exactix - API Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60

  2. resolved Apr 13, 2026, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 9, 2026

Customers will see delays with domain transfers.

Detected by Pingoru
Apr 09, 2026, 10:02 AM UTC
Resolved
Apr 09, 2026, 01:25 PM UTC
Duration
3h 23m
Timeline · 7 updates
  1. investigating Apr 09, 2026, 10:02 AM UTC

    We are investigating an issue with the domain transfer page. Customers might not be able to initiate a domain transfer.

  2. investigating Apr 09, 2026, 10:04 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "Customers will see delays with domain transfers."

  3. investigating Apr 09, 2026, 10:04 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident message [We are investigating an issue with the domain transfer page. Customers might not be able to initiate a domain transfer.] has changed as [We are continuing to investigate this issue.]. Statuspage incident component [Domains] status [operational] has changed as [degraded_performance]. " on alert: "Customers will see delays with domain transfers."

  4. investigating Apr 09, 2026, 10:29 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED]. Statuspage incident message [We are continuing to investigate this issue.] has changed as [The issue has been identified and a fix is being implemented.]. " on alert: "Customers will see delays with domain transfers."

  5. investigating Apr 09, 2026, 11:13 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING]. Statuspage incident message [The issue has been identified and a fix is being implemented.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Customers will see delays with domain transfers."

  6. investigating Apr 09, 2026, 11:22 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED]. Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [This incident has been resolved.]. Statuspage incident component [Domains] status [degraded_performance] has changed as [operational]. " on alert: "Customers will see delays with domain transfers."

  7. resolved Apr 09, 2026, 01:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 7, 2026

[StatusCake] Sunshine 811 Web Site status is Down

Detected by Pingoru
Apr 07, 2026, 04:36 PM UTC
Resolved
Apr 07, 2026, 04:48 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Apr 07, 2026, 04:36 PM UTC

    Test Name: Sunshine 811 Web Site Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60

  2. investigating Apr 07, 2026, 04:37 PM UTC

    [Comment from Opsgenie]John Nida acknowledged alert: "[StatusCake] Sunshine 811 Web Site status is Down"

  3. resolved Apr 07, 2026, 04:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 2, 2026

Connectivity issues

Detected by Pingoru
Apr 02, 2026, 07:11 PM UTC
Resolved
Apr 03, 2026, 09:43 AM UTC
Duration
14h 32m
Timeline · 5 updates
  1. investigating Apr 02, 2026, 07:11 PM UTC

    We're investigating issues with loading sites.

  2. investigating Apr 02, 2026, 07:18 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED]. Statuspage incident message [We're investigating issues with loading sites.] has changed as [The issue has been identified and a fix is being implemented.]. " on alert: "Connectivity issues"

  3. investigating Apr 02, 2026, 07:24 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING]. Statuspage incident message [The issue has been identified and a fix is being implemented.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Connectivity issues"

  4. investigating Apr 02, 2026, 07:29 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED]. Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [This incident has been resolved.]. " on alert: "Connectivity issues"

  5. resolved Apr 03, 2026, 09:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 11, 2026

Customers unable to create new trial sites

Detected by Pingoru
Feb 11, 2026, 08:18 PM UTC
Resolved
Feb 11, 2026, 08:19 PM UTC
Duration
27s
Timeline · 2 updates
  1. investigating Feb 11, 2026, 08:18 PM UTC

    We're investigating issues with new trial creation.

  2. resolved Feb 11, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Sunshine 811 downtime and outages?

Pingoru polls Sunshine 811's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sunshine 811 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sunshine 811 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sunshine 811 for free

5 free monitors · No credit card required