Home
/
Status
/
Service
Error tracking and application monitoring for developers.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Degraded
Checked 1h ago
31
Components
0
Active incidents
0
Maintenance
0%
90d uptime
Delays with notifications
Mar 12, 7:27 PM
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
1 known history days
31
Components tracked
0 outage, 1 degraded
50
Incidents indexed
0 active right now
11
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Outbound SMS via Twilio
Degraded Performance
API
Operational
AWS cloudFront
Operational
AWS dynamodb-ap-southeast-1
Operational
AWS dynamodb-eu-central-1
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
0
operational days
1
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
We had a backlog in our notifications queue that prevented timely delivery of alerts to channels such as Email, Slack, etc. The backlog has been processed as of 19:20 UTC. Our autoscaling rules for this service had a monitoring gap that prevented a scale-out to maintain a low latency on the queue. This monitoring gap has been resolved.
This incident has been resolved.
This incident has been resolved.
The EU API has been restored.
This incident has been resolved.
Our systems were affected by the DynamoDB outage in AWS' us-east-1 region. Impacts included not being able to log use the web app, uptime checks not being executed on time, and check-ins being falsely reported as missing. We are evaluating what steps we can take to mitigate these kinds of impacts from this kind of outage in the future. Additionally, our status page was not updated in a timely manner due to our not having configured various AWS services as dependent components of our status page. We have fixed that issue, so future AWS outages will result in our status page automatically being updated.
We had an interruption in processing of check-in alerts and in-app stats from about 12:30 to about 13:30 UTC. This may have resulted in a failure or a delay in reporting check-ins that went missing during that period.
The backlog has been processed and all systems are running normally.
This incident has been resolved.
The backlog has been fully processed, so all Insights events should be ingested and available.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed. Some check-ins may have falsely reported as being missing during this window. We will work on improving that for future maintenance events.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Honeybadger status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.honeybadger.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 31 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Web Application | Operational | Component | Not recorded |
API | Operational | Component | Not recorded |
Outbound SMS via Twilio | Degraded Performance | Component | Not recorded |
Payments via Stripe | Operational | Component | Not recorded |
AWS cloudFront | Operational | Component | Not recorded |
AWS route53 | Operational | Component | Not recorded |
Pusher Pusher REST API | Operational | Component | Not recorded |
Pusher WebSocket client API | Operational | Component | Not recorded |
Pusher Presence channels | Operational | Component | Not recorded |
Pusher Webhooks | Operational | Component | Not recorded |
Slack Notifications | Operational | Component | Not recorded |
Slack Apps/Integrations/APIs | Operational | Component | Not recorded |
PagerDuty Events API (US) | Operational | Component | Not recorded |
PagerDuty Events API (EU) | Operational | Component | Not recorded |
Outbound email | Operational | Component | Not recorded |
AWS dynamodb-eu-central-1 | Operational | Component | Not recorded |
AWS dynamodb-us-east-1 | Operational | Component | Not recorded |
AWS dynamodb-ap-southeast-1 | Operational | Component | Not recorded |
AWS dynamodb-eu-west-2 | Operational | Component | Not recorded |
AWS dynamodb-us-west-2 | Operational | Component | Not recorded |
AWS ecs-us-east-1 | Operational | Component | Not recorded |
AWS ecs-eu-central-1 | Operational | Component | Not recorded |
AWS elb-eu-central-1 | Operational | Component | Not recorded |
AWS elb-us-east-1 | Operational | Component | Not recorded |
AWS lambda-eu-central-1 | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Honeybadger is currently marked as Degraded in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
