All Systems Operational
API Operational
90 days ago
99.96 % uptime
Today
Web Application Operational
90 days ago
99.95 % uptime
Today
Public Dashboards Operational
90 days ago
99.96 % uptime
Today
Check Scheduler Operational
90 days ago
99.94 % uptime
Today
Browser check runtime Operational
90 days ago
99.96 % uptime
Today
Deployments Operational
90 days ago
99.92 % uptime
Today
Alerting 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
Jul 3, 2022

No incidents reported today.

Jul 2, 2022

No incidents reported.

Jul 1, 2022

No incidents reported.

Jun 30, 2022

No incidents reported.

Jun 29, 2022

No incidents reported.

Jun 28, 2022

No incidents reported.

Jun 27, 2022
Resolved - A fix was released regarding this issue, our parsing is now more forgiving and will allow invalid urls to be parsed without causing any side effects. The faulty request, prefixed by "Invalid URL:", will still be available in the network tab for a browser check result.
Jun 27, 14:36 UTC
Identified - We got some reports from our users that they see errors like "Cannot set property 'finishedAt' of undefined" or "ERR_INVALID_URL". After an investigation we identified that the issue happens with websites that have casalemedia.com integrated. During the check execution, we receive a URL that can't be parsed by NodeJS and this causes the errors. In order to avoid this, you can add the snippet below to your affected checks. We will make sure our parsing is more forgiving and the root cause of the failure is not polluted by our errors.
await page.route('**/*', (route) => {
return route.request().url().includes('casalemedia')
? route.abort()
: route.continue()
})

Jun 26, 16:09 UTC
Jun 26, 2022
Jun 25, 2022

No incidents reported.

Jun 24, 2022

No incidents reported.

Jun 23, 2022

No incidents reported.

Jun 22, 2022

No incidents reported.

Jun 21, 2022
Resolved - Our provider has informed us that the incident is resolved
Jun 21, 07:55 UTC
Monitoring - Our provider has informed us that a fix was in place and the issue is now being monitored
Jun 21, 07:43 UTC
Identified - We traced the problem to our authentication provider. The issue is currently only affecting our webapp. We are reaching out to them.
Jun 21, 07:05 UTC
Update - We are continuing to investigate this issue.
Jun 21, 06:59 UTC
Investigating - There was a spike in errors at our system. We are investigating the root cause.
Jun 21, 06:58 UTC
Jun 20, 2022

No incidents reported.

Jun 19, 2022

No incidents reported.