Disclaimer: Uptime percentages displayed on this status page do not represent SLA commitments. Refer to your service agreement for information on how SLA performance is evaluated, contact support@synopticdata.com for more information.
Services
Operational
90 days ago
100.0
% uptime
Today
Weather API
Operational
90 days ago
100.0
% uptime
Today
Push data streaming
Operational
90 days ago
100.0
% uptime
Today
Notification Service
Operational
90 days ago
100.0
% uptime
Today
Data platform
Operational
90 days ago
100.0
% uptime
Today
Data Ingest
Operational
90 days ago
100.0
% uptime
Today
Data storage and processing
Operational
90 days ago
100.0
% uptime
Today
Availability Monitoring
Operational
Data providers
Operational
Government and other major datasets
Operational
Road Weather Providers
Operational
Private/Commercial
Operational
Web Authentication
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.
Related
No incidents or maintenance related to this downtime.
Resolved -
We are confident in our remediations and plan to share a postmortem this week.
May 10, 17:36 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 10, 06:22 UTC
Identified -
Synoptic engineering teams are addressing an issue which has increased the latency of observations flowing through our system. Currently many datasets are 20 minutes or more later than expected.
May 10, 04:04 UTC
Resolved -
The RAWS data platform has returned to expected functionality.
May 8, 13:32 UTC
Update -
We are continuing to work on a fix for this issue.
May 8, 11:21 UTC
Identified -
Synoptic has been unable to pull RAWS data from our source. We are also investigating a (likely) un related disruption to the SNOTEL data acquisition.
May 8, 04:22 UTC
Resolved -
This incident has been resolved.
May 6, 20:54 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 6, 18:48 UTC
Identified -
We have identified the source of the disruption and need our upstream vendor to resolve an issue before our systems will be able to receive observations.
May 6, 17:49 UTC