Trackora System Status

This page shows the real-time operational status of every component that powers the Trackora package tracking service. Status indicators update automatically every 60 seconds. Bookmark this page if you want a quick way to check whether a tracking delay is caused by a carrier, your network, or a Trackora service issue.

Monitored Services

API Gateway

The API gateway is the entry point for all requests from the Trackora web application, mobile apps, and third-party integrations. It handles authentication, request routing, and rate limiting. Degraded performance here affects every surface: web, mobile, and API consumers see slower responses or error codes. Normal response time is under 200 ms for 95% of requests.

Database

The PostgreSQL database stores all user accounts, saved parcels, tracking history, and notification preferences. A database incident prevents new parcels from being saved, stops history from loading, and blocks login for users without an active session cookie. The database runs on managed infrastructure with automated daily backups and point-in-time recovery. Recovery point objective (RPO) is 24 hours; recovery time objective (RTO) is under 2 hours for most failure modes.

Tracking Engine

The tracking engine polls carrier APIs and the TrackingMore aggregator to fetch parcel status updates. It runs on a background worker separate from the API gateway so that a spike in tracking volume does not slow down the website. For Premium users, the engine polls every 30 minutes. For free users, statuses are fetched on demand when the page is opened. Degraded status here means fresh status data may be delayed but existing cached statuses remain visible.

Email Notifications

The email notification service dispatches alerts whenever the tracking engine detects a new status event on a parcel. It uses an SMTP relay with queue-based delivery to ensure messages are not lost during brief outages. A degraded status here means notification emails may be delayed by up to 60 minutes; tracking functionality itself is unaffected.

Telegram Bot

The Telegram bot delivers push notifications for users who have linked their Telegram account. It operates independently from email notifications so an issue with one channel does not affect the other. The bot also supports commands for checking parcel status directly inside a Telegram chat.

SLA Expectations

Trackora targets 99.5% monthly uptime for the API gateway and database. Planned maintenance windows are announced at least 24 hours in advance and are scheduled during off-peak hours (02:00–04:00 UTC). Unplanned incidents are resolved within 4 hours for critical services (API, database) and within 8 hours for secondary services (notifications, Telegram bot).

Incident History and Past Outages

All significant incidents — those affecting service availability for more than 5 minutes — are recorded and investigated. Post-mortems for major incidents are published within 5 business days. Common causes of past incidents include upstream carrier API rate limiting (which causes tracking delays without affecting Trackora availability directly), database connection pool exhaustion during traffic spikes, and email relay quota limits during high-volume notification batches.

Carrier-side issues — for example a Chinese postal carrier taking their API offline during a public holiday — do not register as a Trackora service incident because Trackora has no control over third-party carrier uptime. If a specific carrier shows stale data while all Trackora services are green, the issue is on the carrier side. Trackora automatically retries failed carrier requests on the next polling cycle.

What to Do During an Incident

Trackora — Package Tracking · Pricing · API Docs