IronWorker degraded performance
This incident has been resolved.
Home
/
Status
/
Service
Serverless application tools for background tasks and messaging queues.
Source
auto
Category
Cloud
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 19m ago
6
Components
0
Active incidents
0
Maintenance
50%
90d uptime
IronWorker degraded performance
Jan 18, 10:47 PM
Normalized official status-page data for incidents, maintenance, components, and history.
50%
Known uptime
2 known history days
6
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
13
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Dashboard
Operational
IronCache
Operational
IronMQ v3 (AWS EU-West)
Operational
IronMQ v3 (AWS US-East)
Operational
IronWorker Dedicated
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
1
maintenance days
88
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
Our engineering team is actively resolving the situation, and undertaking necessary steps to recover the system. We expect to post an update momentarily.
This incident has been resolved.
Iron has completed a review of its systems and the Log4j security issue does not affect Iron's services.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
IronWorker customers could experience issues while pushing tasks to Public Cluster on March 14 between 12:00 am UTC and 6:30 am UTC. We've resolved the issue. Our development team is monitoring the situation.
Amazon performed an upgrade of our PostgreSQL DB version. This DB stores logins, passwords, tokens and other information about our customers. While upgrading they shutted down the database instance, performed the upgrade, and restarted the database instance. As a result, you could see HTTP 401 errors in your logs between 09:28 am UTC and 09:45 am UTC. Here is more information: https://forums.aws.amazon.com/ann.jspa?annID=8176
Scheduled and completed maintenance windows are separated from incidents.
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.
The scheduled maintenance has been completed.
Uptimus tracks the official Ironio status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.iron.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 6 of 6 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
IronMQ v3 (AWS US-East) Migrating the cluster to new infrastructure... | Operational | Component | Not recorded |
IronMQ v3 (AWS EU-West) | Operational | Component | Not recorded |
IronCache | Operational | Component | Not recorded |
Dashboard hud-e.iron.io | Operational | Component | Not recorded |
IronWorker Dedicated | Operational | Component | Not recorded |
IronWorker Public | 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.
Ironio is currently marked as Operational 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.