HostHatch Outage History

HostHatch is up right now

Pingoru has recorded 39 incidents for HostHatch: 39 in the last 12 months and 30 in the last 90 days.

Source: status.hosthatch.com

39incidents recorded
39last 12 months
30last 90 days
8 minutestypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking HostHatch 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 202600 of 720 (0%)
May 202640 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 2026181 of 744 (0%)
September 202640 of 720 (0%)
October 2026101 of 744 (0%)
November 202600 of 97 (0%)

Incidents, newest first

Minor August 11, 2026 Network: Singapore: down for 35 seconds 35s Network: Singapore

Started Aug 11, 2026, 12:50 PM UTC· resolved Aug 11, 2026, 12:50 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major August 7, 2026 Network: Oslo: incident detected for 13m 13m Network: Oslo

Started Aug 07, 2026, 06:50 AM UTC· resolved Aug 07, 2026, 07:03 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major August 7, 2026 Network: Oslo: down for 15 minutes 15m Network: Oslo

Started Aug 07, 2026, 06:50 AM UTC· resolved Aug 07, 2026, 07:05 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 7, 2026 Network: Oslo: incident detected for 2m 2m Network: Oslo

Started Aug 07, 2026, 06:41 AM UTC· resolved Aug 07, 2026, 06:43 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 7, 2026 Network: Oslo: down for 2 minutes 2m Network: Oslo

Started Aug 07, 2026, 06:41 AM UTC· resolved Aug 07, 2026, 06:43 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major August 3, 2026 Network: Vienna: incident detected for 14m 14m Network: Vienna

Started Aug 03, 2026, 03:11 PM UTC· resolved Aug 03, 2026, 03:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major August 3, 2026 Network: Vienna: down for 14 minutes 14m Network: Vienna

Started Aug 03, 2026, 03:11 PM UTC· resolved Aug 03, 2026, 03:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 17, 2026 Network: New York: incident detected for 5m 5m Network: New York

Started May 17, 2026, 12:16 PM UTC· resolved May 17, 2026, 12:21 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 17, 2026 Network: New York: down for 5 minutes 5m Network: New York

Started May 17, 2026, 12:16 PM UTC· resolved May 17, 2026, 12:21 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 12, 2026 Network: Hong Kong: incident detected for 35s 35s Network: Hong Kong

Started May 12, 2026, 10:13 PM UTC· resolved May 12, 2026, 10:13 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 12, 2026 Network: Hong Kong: down for 35 seconds 35s Network: Hong Kong

Started May 12, 2026, 10:13 PM UTC· resolved May 12, 2026, 10:13 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major March 19, 2026 Network: Singapore: incident detected for 13m 13m Network: Singapore

Started Mar 19, 2026, 12:15 PM UTC· resolved Mar 19, 2026, 12:29 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major March 13, 2026 Network: Los Angeles: incident detected for 41m 41m Network: Los Angeles

Started Mar 13, 2026, 01:27 PM UTC· resolved Mar 13, 2026, 02:08 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 3, 2026 Network: Vienna: incident detected for 1m 1m Network: Vienna

Started Feb 03, 2026, 11:38 PM UTC· resolved Feb 03, 2026, 11:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →