Degraded / minor incident EasyPost outage dossier
easypost.com · Official status page (Statuspage-compatible JSON)
Known long-running issues (limited scope, not counted in the headline): Scheduled Upstream USPS API Maintenance · Database Maintenance · why
Official status now
Degraded / minor incident Degraded / minor incident
partial 2 known long-running issues provider's page says: Operational checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Storm: official status: Degraded / minor incident
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 8 maintenance
- 1 critical
- 2 none
- 1 major
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 12.7 hScheduled Upstream USPS API Maintenancemaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-19resolved
- → resolved · lasted 55 minElevated errors for Amazon Shippingcritical resolved · Amazon Shipping · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-18resolvedcounted as minor (limited scope)
- → resolved · lasted 2.3 hUpstream USPS API Intermittent Outage - Pickupsnone resolved · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-18resolved
- → resolved · lasted 13.5 hScheduled Upstream USPS API Maintenancemaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-18resolved
- · ongoingDatabase Maintenancemaintenance scheduled · API · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-17stale / unchanged · open 4 daysupdated 4 days agoknown long-running issue
- · ongoingScheduled Upstream USPS API Maintenancemaintenance scheduled · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-17stale / unchanged · open 4 daysupdated 4 days agoknown long-running issue
- → resolved · lasted 25 minElevated Errors Core APImajor resolved · API · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-11resolvedcounted as minor (limited scope)
- → resolved · lasted Elevated Errors Core APInone resolved · official notice ↗ · replay & discussscope not statedstarted 2026-11-11resolved
- → resolved · lasted 5.1 daysScheduled Upstream USPS API Maintenancemaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-10resolved
- → resolved · lasted 4.9 daysScheduled Upstream USPS API Maintenancemaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-10resolved
- → resolved · lasted 2.5 daysScheduled Upstream USPS API Maintenancemaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-11-10resolved
- → resolved · lasted 15.7 daysService Disruption with USPS Payments APImaintenance completed · USPS APIs · official notice ↗ · replay & discuss1 of 6 componentsstarted 2026-10-30resolved
Related services
- no official feedUPSno official feed→
- no official feedFedExno official feed→
- no official feedDHLno official feed→
- Degraded / minor incidentShippoDegraded / minor incident→
- OperationalShipStationOperational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.