Semaphore incident
Delivering webhooks delays between Github and Semaphore
Affected components
Update timeline
- investigating Feb 03, 2026, 03:46 PM UTC
We are currently investigating this issue.
- identified Feb 03, 2026, 05:34 PM UTC
Webhook delivery delays between GitHub and Semaphore appear to be caused by degraded performance on GitHub’s side. GitHub is currently reporting an active incident that appears related. We are monitoring the situation closely and will provide updates as GitHub resolves the issue.
- monitoring Feb 03, 2026, 07:11 PM UTC
GitHub has posted an update indicating recovery of the aforementioned issue. We continue monitoring Semaphore closely as things stabilize. (GitHub Status: https://www.githubstatus.com/incidents/f314nlctbfs5)
- resolved Feb 03, 2026, 07:50 PM UTC
This incident has been resolved.
Looking to track Semaphore downtime and outages?
Pingoru polls Semaphore's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Semaphore reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Semaphore alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required