Is Happo down?
Last checked 2m agoNo incidents right now.
Happo is operational right now. Last checked 2m ago; the most recent incident resolved 2d ago.
Real-time Happo status, recent outages, and incident history: pulled directly from Happo's official status page at happo.statuspage.io every 5 minutes. Pingoru tracks 8 Happo services and has captured 2 incidents in the last 90 days (98.68% uptime). Get email, Slack, Discord, or webhook alerts the moment Happo reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- ChromeFirefoxEdgeSafari
Timeline · 2 updates
- investigating · Oct 27, 2026, 09:47 PM UTC
Our infrastructure provider is having a problem that stops us from adding rendering capacity. Happo jobs are still being processed, but during busy periods screenshots may take noticeably longer than usual and jobs may queue. Chrome, Firefox, Safari, and Edge renders are affected; iOS Safari and iPad Safari are not. We’re working with the provider to restore normal capacity and will post an update when we know more.
- resolved · Oct 28, 2026, 01:42 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- API
Timeline · 2 updates
- investigating · Aug 17, 2026, 02:54 PM UTC
We’re seeing errors coming from our own API calls to GitHub causing most jobs to fail on our end as well. We’re investigating this right now.
- resolved · Aug 17, 2026, 06:33 PM UTC
A GitHub outage caused some of our API endpoints started to fail. To reduce the impact we briefly turned off some communication with GitHub which made things stabilize on our side. At this time, no Happo statuses could be posted to GitHub PRs and commits. At 18.11 UTC we saw things starting to stabilize and briefly after we were back in a good state again.
Latest: A GitHub outage caused some of our API endpoints started to fail. To reduce the impact we briefly turned off some communication with GitHub which made things stabilize on our side.…
-
Incident record
Since April 2026 · Statuspage by Atlassian · 8 components checked every 5 minutesThe longest incident in the last year, Slower screenshot processing on October 27, 2026, ran for 4 hours.
Most affected components, last 12 months
- API2
- Chrome1
- Edge1
- Firefox1
- Safari1
Latest incidents
- Slower screenshot processing
Our infrastructure provider is having a problem that stops us from adding rendering capacity. Happo jobs are still being processed, but during busy periods…
- API failures
We’re seeing errors coming from our own API calls to GitHub causing most jobs to fail on our end as well. We’re investigating this right now.
- Timeouts and failed API requests
During a window of about 7 minutes, our API and web application served at happo.io was unresponsive. This was caused by a configuration mistake in our backend…
- Slower screenshot processing ResolvedStarted Oct 27, 2026, 09:47 PM UTC · Resolved Oct 28, 2026, 01:42 AM UTC · 3h 55m
- API failures ResolvedStarted Aug 17, 2026, 02:54 PM UTC · Resolved Aug 17, 2026, 05:33 PM UTC · 2h 38m