All Systems Operational

About This Site

Welcome to Sunshine 811's System Status Information Page.

This page is used to assist in communicating information regarding both planned and unplanned system performance and maintenance issues.

For additional status and uptime based on specific times during the past week, please visit http://statuscake.sunshine811.com

Primary Internet Service Provider Operational
90 days ago
100.0 % uptime
Today
Alternate Internet Service Providers Operational
90 days ago
100.0 % uptime
Today
DNS Services Operational
90 days ago
100.0 % uptime
Today
Exactix Operational
90 days ago
100.0 % uptime
Today
IRTHNet Member Ticket Management System Operational
90 days ago
100.0 % uptime
Today
IRTHNet Positive Response System ? Operational
90 days ago
100.0 % uptime
Today
IRTHNet Outbound Transmission Queues ? Operational
90 days ago
100.0 % uptime
Today
Telephone Service ? Operational
90 days ago
100.0 % uptime
Today
Third Party Service Providers ? Operational
Squarespace Operational
Shopify Checkout ? Operational
Shopify Storefront ? Operational
StatusPage.io Email Notifications Operational
StatusPage.io SMS Notifications Operational
StatusPage.io Hosted Pages Operational
StatusPage.io Public Metrics Operational
GoToMeeting, GoToWebinar, GoToTraining, & OpenVoice GoToMeeting Operational
Jira Service Management Jira Service Management Email Requests Operational
Jira Service Management Service Portal Operational
Opsgenie Public Website Operational
Opsgenie Incident Flow Operational
Opsgenie Alert Flow Operational
Opsgenie Email Notification Delivery Operational
Opsgenie SMS Notification Delivery Operational
Opsgenie Voice Notification Delivery Operational
Opsgenie Mobile Notification Delivery Operational
Opsgenie Heartbeat Monitoring Operational
Opsgenie Incoming Email Service Operational
Opsgenie Web Application Operational
Opsgenie Mobile Application Operational
Opsgenie Incoming Call Routing Operational
Test Component - Please disregard ? Operational
90 days ago
100.0 % uptime
Today
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.
Past Incidents
Jan 18, 2021

No incidents reported today.

Jan 17, 2021

No incidents reported.

Jan 16, 2021

No incidents reported.

Jan 15, 2021

No incidents reported.

Jan 14, 2021

No incidents reported.

Jan 13, 2021
Resolved - This incident has been resolved.
Jan 13, 14:31 EST
Update - [Comment from Opsgenie]George Demas acknowledged alert: "[StatusCake] IRTHNet Positive Response status is Down"
Jan 13, 14:29 EST
Investigating - Test Name: IRTHNet Positive Response
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 13, 14:27 EST
Resolved - This incident has been resolved.
Jan 13, 14:30 EST
Update - [Comment from Opsgenie]George Demas acknowledged alert: "[StatusCake] IRTHNet Member Ticket Management status is Down"
Jan 13, 14:29 EST
Investigating - Test Name: IRTHNet Member Ticket Management
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 30
Jan 13, 14:28 EST
Resolved - This incident has been resolved.
Jan 13, 14:26 EST
Investigating - Test Name: Windstream Router - Maitland
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 13, 14:25 EST
Resolved - This incident has been resolved.
Jan 13, 14:16 EST
Update - [Comment from Opsgenie]David Jolly acknowledged alert: "[StatusCake] Windstream Router - Maitland status is Down"
Jan 13, 14:10 EST
Investigating - Test Name: Windstream Router - Maitland
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 13, 14:09 EST
Resolved - This incident has been resolved.
Jan 13, 14:12 EST
Investigating - Test Name: Windstream Router - DeBary
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 13, 14:10 EST
Resolved - This incident has been resolved.
Jan 13, 13:57 EST
Update - [Comment from Opsgenie]David Jolly acknowledged alert: "[StatusCake] Windstream Router - Maitland status is Down"
Jan 13, 13:55 EST
Investigating - Test Name: Windstream Router - Maitland
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 13, 13:55 EST
Jan 12, 2021
Resolved - This incident has been resolved.
Jan 12, 07:28 EST
Update - [Comment from Opsgenie]David Jolly acknowledged alert: "[StatusCake] IRTHNet Member Ticket Management status is Down"
Jan 12, 07:28 EST
Investigating - Test Name: IRTHNet Member Ticket Management
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 30
Jan 12, 07:27 EST
Jan 11, 2021

No incidents reported.

Jan 10, 2021

No incidents reported.

Jan 9, 2021
Resolved - This incident has been resolved.
Jan 9, 09:14 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "Connectivity Issues"
Jan 8, 18:57 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [RESOLVED].
Statuspage incident message [We are continuing to monitor for any further issues.] has changed as [This incident has been resolved.]. " on alert: "Connectivity Issues"
Jan 8, 15:38 EST
Update - [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.].
Statuspage incident component [Site Loading] status [partial_outage] has changed as [operational].
Statuspage incident component [Domains] status [partial_outage] has changed as [operational].
Statuspage incident component [Commerce] status [partial_outage] has changed as [operational].
Statuspage incident component [Accounts & Billing] status [partial_outage] has changed as [operational].
Statuspage incident component [G Suite] status [partial_outage] has changed as [operational].
Statuspage incident component [Site Editing] status [partial_outage] has changed as [operational]. " on alert: "Connectivity Issues"
Jan 8, 15:29 EST
Update - [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: "Connectivity Issues"
Jan 8, 15:28 EST
Update - [Comment from Opsgenie]System noted: "Following components are added: [Domains,Accounts & Billing,G Suite]. " on alert: "Connectivity Issues"
Jan 8, 15:25 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We're investigating errors while connecting to some Squarespace sites.] has changed as [We are continuing to investigate this issue.].
Following components are added: [Commerce]. " on alert: "Connectivity Issues"
Jan 8, 15:23 EST
Investigating - We're investigating errors while connecting to some Squarespace sites.
Jan 8, 15:23 EST
Jan 8, 2021
Resolved - This incident has been resolved.
Jan 8, 13:07 EST
Investigating - Test Name: Coursettra
Status Code: 503
Status Text:
Check Rate: 60
Jan 8, 13:06 EST
Resolved - This incident has been resolved.
Jan 8, 08:22 EST
Investigating - Test Name: IRTHNet Member Ticket Management
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 30
Jan 8, 08:21 EST
Jan 7, 2021
Resolved - This incident has been resolved.
Jan 7, 05:02 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 3 (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 7, 02:45 EST
Resolved - This incident has been resolved.
Jan 7, 05:02 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 2 (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 7, 02:45 EST
Resolved - This incident has been resolved.
Jan 7, 05:01 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 1 (HTTP XML/REST Value) Down"
Jan 7, 03:49 EST
Investigating - Last Message From Sensor : Node Amps_Ln_1 not found in xml result.
Jan 7, 02:43 EST
Resolved - This incident has been resolved.
Jan 7, 05:01 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Watts Total (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node RMS_Watts_Tot not found in xml result.
Jan 7, 02:45 EST
Resolved - This incident has been resolved.
Jan 7, 05:01 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 2 (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_2 not found in xml result.
Jan 7, 02:45 EST
Resolved - This incident has been resolved.
Jan 7, 05:01 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 3 (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_3 not found in xml result.
Jan 7, 02:45 EST
Resolved - This incident has been resolved.
Jan 7, 05:01 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 1 (HTTP XML/REST Value) Down"
Jan 7, 03:50 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_1 not found in xml result.
Jan 7, 02:46 EST
Jan 6, 2021
Resolved - This incident has been resolved.
Jan 6, 20:08 EST
Update - [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"
Jan 6, 17:08 EST
Update - [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.].
Statuspage incident component [Site Loading] status [major_outage] has changed as [operational].
Statuspage incident component [Site Editing] status [major_outage] has changed as [operational]. " on alert: "Connectivity Issues"
Jan 6, 17:04 EST
Update - [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: "Connectivity Issues"
Jan 6, 16:51 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident message [We are currently investigating this issue.] has changed as [We are continuing to investigate this issue.].
Following components are added: [Site Editing]. " on alert: "Connectivity Issues"
Jan 6, 16:48 EST
Investigating - We are currently investigating this issue.
Jan 6, 16:48 EST
Resolved - This incident has been resolved.
Jan 6, 20:07 EST
Update - [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 [Site Loading] status [degraded_performance] has changed as [operational]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 14:41 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [INVESTIGATING] has changed as [MONITORING].
Statuspage incident message [We are currently investigating this issue.] has changed as [A fix has been implemented and we are monitoring the results.]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 14:25 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident status [MONITORING] has changed as [INVESTIGATING].
Statuspage incident message [A fix has been implemented and we are monitoring the results.] has changed as [We are currently investigating this issue.]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 13:08 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Background Images with Image Effects Enabled Fail to Load] is updated as [Changes Aren't Appearing on Live Site and Background Images with Image Effects Enabled Fail to Load]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 12:56 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident update request sent with no changes on fields " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 12:53 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Background Images with Image Effects Enabled Fail to Load; S] is updated as [Background Images with Image Effects Enabled Fail to Load]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 12:52 EST
Update - [Comment from Opsgenie]System noted: "Statuspage incident name [Background Images with Image Effects Enabled Fail to Load] is updated as [Background Images with Image Effects Enabled Fail to Load; S]. " on alert: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 12:51 EST
Update - [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: "Background Images with Image Effects Enabled Fail to Load"
Jan 6, 12:09 EST
Investigating - The issue has been identified and a fix is being implemented.
Jan 6, 11:48 EST
Resolved - This incident has been resolved.
Jan 6, 09:49 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[StatusCake] IRTHNet Positive Response status is Down"
Jan 6, 09:49 EST
Investigating - Test Name: IRTHNet Positive Response
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 6, 09:49 EST
Jan 5, 2021
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Watts Total (HTTP XML/REST Value) Down"
Jan 5, 17:10 EST
Investigating - Last Message From Sensor : Node RMS_Watts_Tot not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 2 (HTTP XML/REST Value) Down"
Jan 5, 17:10 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 5, 17:10 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Amps 2 (HTTP XML/REST Value) Down"
Jan 5, 17:10 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 5, 17:10 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 2 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_2 not found in xml result.
Jan 5, 17:08 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 3 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Voltage 1 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_1 not found in xml result.
Jan 5, 17:08 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 3 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_3 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Voltage 1 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_1 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Amps 1 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node Amps_Ln_1 not found in xml result.
Jan 5, 17:08 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor (HADES-02)] EKM Meter Data Watts Total (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Watts_Tot not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Amps 3 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Amps 1 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node Amps_Ln_1 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Voltage 2 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_2 not found in xml result.
Jan 5, 17:09 EST
Resolved - This incident has been resolved.
Jan 5, 17:10 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[PRTG] [PRTG Network Monitor] EKM Meter Data Voltage 3 (HTTP XML/REST Value) Down"
Jan 5, 17:09 EST
Investigating - Last Message From Sensor : Node RMS_Volts_Ln_3 not found in xml result.
Jan 5, 17:09 EST
Jan 4, 2021
Resolved - This incident has been resolved.
Jan 4, 11:57 EST
Update - [Comment from Opsgenie]Bill Heath acknowledged alert: "[StatusCake] Windstream Router - DeBary status is Down"
Jan 4, 11:47 EST
Investigating - Test Name: Windstream Router - DeBary
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 60
Jan 4, 11:46 EST
Resolved - This incident has been resolved.
Jan 4, 07:13 EST
Update - [Comment from Opsgenie]David Jolly acknowledged alert: "[StatusCake] IRTHNet Member Ticket Management status is Down"
Jan 4, 07:12 EST
Investigating - Test Name: IRTHNet Member Ticket Management
Status Code: 0
Status Text: Timeout / Connection Refused
Check Rate: 30
Jan 4, 07:11 EST
Resolved - This incident has been resolved.
Jan 4, 06:36 EST
Investigating - Last Message From Sensor : Node Amps_Ln_1 not found in xml result.
Jan 4, 06:11 EST
Resolved - This incident has been resolved.
Jan 4, 06:36 EST
Investigating - Last Message From Sensor : Node RMS_Watts_Tot not found in xml result.
Jan 4, 06:10 EST
Resolved - This incident has been resolved.
Jan 4, 06:36 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 4, 06:09 EST
Resolved - This incident has been resolved.
Jan 4, 06:36 EST
Investigating - Last Message From Sensor : Node Amps_Ln_1 not found in xml result.
Jan 4, 06:11 EST
Resolved - This incident has been resolved.
Jan 4, 06:36 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 4, 06:11 EST
Resolved - This incident has been resolved.
Jan 4, 06:35 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 4, 06:10 EST
Resolved - This incident has been resolved.
Jan 4, 06:35 EST
Investigating - Last Message From Sensor : Node Amps_Ln_2 not found in xml result.
Jan 4, 06:10 EST
Resolved - This incident has been resolved.
Jan 4, 06:35 EST
Investigating - Last Message From Sensor : Node RMS_Watts_Tot not found in xml result.
Jan 4, 06:11 EST