Home
/
Status
/
Service
Rust package registry for crates.
Source
auto
Category
SaaS
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 47m ago
2
Components
0
Active incidents
0
Maintenance
0%
90d uptime
crates.io slowness
Jun 14, 1:20 AM
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
4 known history days
2
Components tracked
0 outage, 0 degraded
47
Incidents indexed
0 active right now
17
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
crates.io
Operational
docs.rs
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
0
operational days
0
degraded days
4
outage days
0
maintenance days
86
unknown days
Latest outages and degradations detected from the official status page.
The primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded.
This incident has been resolved.
All endpoints are now operational and available again.
The indexes are now back to normal operations.
The background worker has caught up, and crate publishes are now updating normally in both indexes.
Everything continues to look stable, so we can consider this resolved.
All published crates have been synced to the Git index, and there is now no backlog.
This incident has been resolved.
The Git index has caught up and is now up to date.
Crates published since the background workers were restarted are now appearing in the index, and the backlog of background jobs has been processed successfully.
Scheduled and completed maintenance windows are separated from incidents.
Everything continues to work as intended so we will consider this migration successful. If you notice any issues, please contact us via https://github.com/rust-lang/crates.io/issues/new/choose.
The scheduled maintenance has been completed.
Deployment complete.
Maintenance was completed successfully.
Database maintenance is now complete.
The scheduled maintenance has been completed.
Scheduled maintenance finished successfully.
The scheduled maintenance has been completed.
Scheduled maintenance finished successfully.
Scheduled maintenance finished successfully.
Uptimus tracks the official Cratesio status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.crates.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 2 of 2 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
crates.io | Operational | Component | Not recorded |
docs.rs | 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.
Cratesio 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.
