Sunshine 811 Outage History

Sunshine 811 is up right now

Sunshine 811 had 32 outages in the last 2 years totaling 57h 13m of downtime — averaging 1.3 incidents per month.

There were 32 Sunshine 811 outages since May 19, 2025 totaling 57h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sunshine811.com

Notice May 16, 2026

[StatusCake] Exactix Heartbeat status is Down

Detected by Pingoru
May 16, 2026, 05:54 AM UTC
Resolved
May 16, 2026, 06:09 AM UTC
Duration
15m
Timeline · 2 updates
  1. investigating May 16, 2026, 05:54 AM UTC

    Test Name: Exactix Heartbeat Status Code: 502 Status Text: Service was detected as Down. Check Rate: 900

  2. resolved May 16, 2026, 06:09 AM 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 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 →

Notice January 21, 2026

All Deployments: Authentication Failures for Newly Created MSP Sub-Accounts

Detected by Pingoru
Jan 21, 2026, 09:38 PM UTC
Resolved
Jan 22, 2026, 11:23 AM UTC
Duration
13h 45m
Timeline · 5 updates
  1. investigating Jan 21, 2026, 09:38 PM UTC

    We are currently investigating an issue causing authentication failures with the authentications for newly created MSP sub-accounts on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

  2. investigating Jan 21, 2026, 09:57 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED]. Statuspage incident message [We are currently investigating an issue causing authentication failures with the authentications for newly created MSP sub-accounts on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.] has changed as [We have identified the cause of authentication failures for newly created MSP sub-accounts and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.]. " on alert: "All Deployments: Authentication Failures for Newly Created MSP Sub-Accounts"

  3. investigating Jan 21, 2026, 10:01 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident impact [NONE] has changed as [MINOR]. " on alert: "All Deployments: Authentication Failures for Newly Created MSP Sub-Accounts"

  4. investigating Jan 21, 2026, 11:32 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [RESOLVED]. Statuspage incident message [We have identified the cause of authentication failures for newly created MSP sub-accounts and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.] has changed as [We have identified the cause of the issue for authentication failures with newly created MSP Sub-accounts on all our deployments and remediation steps have been applied to correct this. If you continue to experience any additional issues related to this, please contact us at https://duo.com/support referencing this incident, (https://status.duo.com/incidents/tymgyq32v7dw).]. Following components are removed: [Admin Panel]. Following components are added: [Core Authentication Service]. " on alert: "All Deployments: Authentication Failures for Newly Created MSP Sub-Accounts"

  5. resolved Jan 22, 2026, 11:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 12, 2026

Connectivity issues - 503 errors

Detected by Pingoru
Jan 12, 2026, 11:05 AM UTC
Resolved
Jan 12, 2026, 02:41 PM UTC
Duration
3h 36m
Timeline · 4 updates
  1. investigating Jan 12, 2026, 11:05 AM UTC

    We’re investigating issues connecting to Squarespace sites.

  2. investigating Jan 12, 2026, 11:10 AM UTC

    [Comment from Opsgenie]David Jolly acknowledged alert: "Connectivity issues - 503 errors"

  3. investigating Jan 12, 2026, 11:27 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [RESOLVED]. Statuspage incident message [We’re investigating issues connecting to Squarespace sites.] has changed as [This incident has been resolved.]. " on alert: "Connectivity issues - 503 errors"

  4. resolved Jan 12, 2026, 02:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 16, 2025

Non-English Template Front Sites

Detected by Pingoru
Dec 16, 2025, 04:08 PM UTC
Resolved
Dec 16, 2025, 04:24 PM UTC
Duration
16m
Timeline · 2 updates
  1. investigating Dec 16, 2025, 04:08 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Dec 16, 2025, 04:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 3, 2025

Site Loading and Editing issues - due to 503 errors

Detected by Pingoru
Nov 03, 2025, 05:40 PM UTC
Resolved
Nov 03, 2025, 06:59 PM UTC
Duration
1h 19m
Timeline · 5 updates
  1. investigating Nov 03, 2025, 05:40 PM UTC

    We are continuing to investigate this issue.

  2. investigating Nov 03, 2025, 05:45 PM UTC

    [Comment from Opsgenie]John Nida acknowledged alert: "Site Loading and Editing issues - due to 503 errors"

  3. investigating Nov 03, 2025, 06:00 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.]. Statuspage incident component [Site Loading] status [partial_outage] has changed as [operational]. Statuspage incident component [Site Editing] status [major_outage] has changed as [operational]. " on alert: "Site Loading and Editing issues - due to 503 errors"

  4. investigating Nov 03, 2025, 06:55 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: "Site Loading and Editing issues - due to 503 errors"

  5. resolved Nov 03, 2025, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

All Deployments: Duo Phone Call and SMS Delivery Failure

Detected by Pingoru
Oct 20, 2025, 06:48 PM UTC
Resolved
Oct 20, 2025, 07:48 PM UTC
Duration
1h
Timeline · 3 updates
  1. investigating Oct 20, 2025, 06:48 PM UTC

    The issue affecting phone-based authentication and SMS delivery has now been resolved. System performance has remained stable, and all services are operating as expected across deployments. We will continue to monitor for any anomalies, but no further impact is anticipated at this time.

  2. investigating Oct 20, 2025, 06:56 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "All Deployments: Duo Phone Call and SMS Delivery Failure"

  3. resolved Oct 20, 2025, 07:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

All Deployments: Email delivery issues

Detected by Pingoru
Oct 20, 2025, 06:45 PM UTC
Resolved
Oct 20, 2025, 07:48 PM UTC
Duration
1h 3m
Timeline · 4 updates
  1. investigating Oct 20, 2025, 06:45 PM UTC

    The issue affecting email delivery has been resolved. System performance has remained stable, and all services are functioning normally across deployments. We’ll continue to monitor to ensure ongoing reliability. Thank you for your patience throughout this incident.

  2. investigating Oct 20, 2025, 06:52 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "All Deployments: Email delivery issues"

  3. investigating Oct 20, 2025, 06:56 PM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "All Deployments: Email delivery issues"

  4. resolved Oct 20, 2025, 07:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 22, 2025

[StatusCake] Technical Support Web Site status is Down

Detected by Pingoru
Sep 22, 2025, 04:48 AM UTC
Resolved
Sep 22, 2025, 04:53 AM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Sep 22, 2025, 04:48 AM UTC

    Test Name: Technical Support Web Site Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 300

  2. resolved Sep 22, 2025, 04:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 3, 2025

Some Commerce features are failing to load

Detected by Pingoru
Sep 03, 2025, 08:39 PM UTC
Resolved
Sep 03, 2025, 08:50 PM UTC
Duration
10m
Timeline · 2 updates
  1. investigating Sep 03, 2025, 08:39 PM UTC

    We're currently investigating an issue that is preventing some Commerce features from loading.

  2. resolved Sep 03, 2025, 08:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 26, 2025

T-Mobile Services SMS Delivery Issue

Detected by Pingoru
Aug 26, 2025, 06:29 AM UTC
Resolved
Aug 26, 2025, 10:18 AM UTC
Duration
3h 49m
Timeline · 4 updates
  1. investigating Aug 26, 2025, 06:29 AM UTC

    We are currently investigating an issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.

  2. investigating Aug 26, 2025, 08:02 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [IDENTIFIED]. Statuspage incident message [We are currently investigating an issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.] has changed as [We have detected the issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.]. " on alert: "T-Mobile Services SMS Delivery Issue"

  3. investigating Aug 26, 2025, 08:14 AM UTC

    [Comment from Opsgenie]System noted: "Statuspage incident status [IDENTIFIED] has changed as [MONITORING]. Statuspage incident message [We have detected the issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.] has changed as [We are starting to see recovery post the fix implemented by our service provider for the issue affecting SMS delivery to phone numbers using T-Mobile Services in the US. Please feel free to check back here or subscribe to updates for the latest information regarding any changes or resolutions.]. " on alert: "T-Mobile Services SMS Delivery Issue"

  4. resolved Aug 26, 2025, 10:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 18, 2025

India VoIP Failures

Detected by Pingoru
Aug 18, 2025, 11:25 AM UTC
Resolved
Aug 18, 2025, 01:12 PM UTC
Duration
1h 46m
Timeline · 2 updates
  1. investigating Aug 18, 2025, 11:25 AM UTC

    We are currently investigating an issue causing phone call authentication failures in India on all of our deployments and are working to correct the issue as soon as possible. Please check back here or subscribe to updates for any changes.

  2. resolved Aug 18, 2025, 01:12 PM UTC

    This incident has been resolved.

Read the full incident report →