Home / Status
Service status
Components
| Component | Endpoint | Status |
|---|---|---|
| API gateway | api.parcelgrid.mywire.org | Operational |
| Package index and downloads | cdn.parcelgrid.mywire.org | Operational |
| Authentication and tokens | api.…/v1/workspace | Operational |
| Web console | parcelgrid.mywire.org | Operational |
| Usage reporting | api.…/v1/usage | Operational |
Regions
| Region | Location | Status |
|---|---|---|
eu-north-1 | Tallinn | Operational |
eu-central-1 | Frankfurt | Operational |
eu-west-1 | Amsterdam | Operational |
Scheduled maintenance
Sundays, 02:00–03:00 UTC: rolling cache reindex. Nodes are drained one at a time, so requests are served from the remaining nodes and no downtime is expected. Windows are announced at least 48 hours in advance when a maintenance step can affect availability.
Incident history
No incidents have been reported in the last 30 days. Incident history is retained for 90 days and is available to workspace owners in the console, including affected workspaces and the error codes returned during the incident.
How this page is measured
- Synthetic requests run every 60 seconds against
api.…/v1/healthand against a signed artifact download from each region. - A component is marked degraded when two consecutive probes fail, and is marked operational after three consecutive successes.
- Availability figures on the home page are computed from these probes over a trailing 30-day window.
Workspace owners can subscribe to incident email in the console. Last updated 28 October 2026.