CoverageBook Outage History

CoverageBook is up right now

Pingoru has recorded 78 incidents for CoverageBook: 55 in the last 12 months and 4 in the last 90 days.

Source: status.coveragebook.com

78incidents recorded
55last 12 months
4last 90 days
47 minutestypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking CoverageBook in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202660 of 720 (0%)
May 202691 of 744 (0%)
June 2026112 of 720 (0%)
July 2026180 of 744 (0%)
August 202630 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 744 (0%)
November 202600 of 61 (0%)

Incidents, newest first

Minor June 30, 2026 Performance recovered –

Started Jun 30, 2026, 02:58 AM UTC· resolved Jun 30, 2026, 02:58 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 30, 2026 Performance recovered –

Started Jun 30, 2026, 01:56 AM UTC· resolved Jun 30, 2026, 01:56 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 29, 2026 Performance recovered –

Started Jun 29, 2026, 07:06 PM UTC· resolved Jun 29, 2026, 07:06 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 26, 2026 Performance recovered –

Started Jun 26, 2026, 03:58 PM UTC· resolved Jun 26, 2026, 03:58 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 26, 2026 Performance recovered –

Started Jun 26, 2026, 04:36 AM UTC· resolved Jun 26, 2026, 04:36 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 26, 2026 Performance recovered –

Started Jun 26, 2026, 01:20 AM UTC· resolved Jun 26, 2026, 01:20 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 4, 2026 Performance recovered –

Started Jun 04, 2026, 11:13 AM UTC· resolved Jun 04, 2026, 11:13 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 1, 2026 Issues with screenshots 1h 35m Current status by service (Data Collection)

Started Jun 01, 2026, 01:21 PM UTC· resolved Jun 01, 2026, 02:56 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 28, 2026 Performance recovered –

Started May 28, 2026, 07:39 PM UTC· resolved May 28, 2026, 07:39 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 28, 2026 Performance recovered –

Started May 28, 2026, 02:42 PM UTC· resolved May 28, 2026, 02:42 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 27, 2026 Performance recovered 1m

Started May 27, 2026, 06:19 PM UTC· resolved May 27, 2026, 06:21 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 27, 2026 Performance recovered –

Started May 27, 2026, 05:16 PM UTC· resolved May 27, 2026, 05:16 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 15, 2026 Performance recovered –

Started May 15, 2026, 08:01 AM UTC· resolved May 15, 2026, 08:01 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 7, 2026 Performance recovered –

Started May 07, 2026, 05:31 PM UTC· resolved May 07, 2026, 05:31 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 7, 2026 Performance recovered –

Started May 07, 2026, 07:58 AM UTC· resolved May 07, 2026, 07:58 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 6, 2026 Performance recovered 25m

Started May 06, 2026, 07:37 AM UTC· resolved May 06, 2026, 08:02 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 6, 2026 Performance recovered –

Started May 06, 2026, 06:56 AM UTC· resolved May 06, 2026, 06:56 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 29, 2026 Performance recovered –

Started Apr 29, 2026, 12:12 PM UTC· resolved Apr 29, 2026, 12:12 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 24, 2026 Performance recovered –

Started Apr 24, 2026, 12:07 PM UTC· resolved Apr 24, 2026, 12:07 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 23, 2026 Performance recovered –

Started Apr 23, 2026, 03:33 PM UTC· resolved Apr 23, 2026, 03:33 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 18, 2026 Performance recovered –

Started Apr 18, 2026, 02:12 PM UTC· resolved Apr 18, 2026, 02:12 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 9, 2026 Application recovered –

Started Apr 09, 2026, 01:16 PM UTC· resolved Apr 09, 2026, 01:16 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major April 9, 2026 The service is currently unavailable 5m Current status by service (Application)

Started Apr 09, 2026, 01:15 PM UTC· resolved Apr 09, 2026, 01:20 PM UTC

  1. investigating Apr 09, 2026, 01:15 PM UTC

    Our service is currently unavailable. We are looking into the cause and will update as soon as we can. We're really sorry for any delays this is causing!

  2. resolved Apr 09, 2026, 01:20 PM UTC

    Normal service has now resumed! Thanks for your patience here.

Read the full incident report →

Major March 27, 2026 Performance went down –

Started Mar 27, 2026, 08:44 PM UTC· resolved Mar 27, 2026, 08:44 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 27, 2026 Performance recovered –

Started Mar 27, 2026, 08:40 PM UTC· resolved Mar 27, 2026, 08:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →