කොන්දේසි
අප්ටයිම්
2025 ඔක්තෝබර් 05, 09:00 PT.
AngryPages status is shown as an operational surface with incident context when traffic, servers, or integrations are under pressure.
The old page's live dashboard value is preserved: current status, incident history, and a clear notice when unusually high traffic may slow some pages.
Daily uptime should summarize recent health without making readers parse a bulky chart before they understand the service state.
The chart idea stays in message2: days before launch, healthy days, future days, and daily status history can be represented compactly when the data is wired.
API and authentication health covers login, sessions, account routes, permissions, and authenticated product actions.
If API/Auth is degraded, readers may see login failures, expired sessions, permission errors, or slow account actions even when public pages still load.
Story delivery health covers public reading, page routing, search, archive navigation, and paid unlock visibility.
If Story Delivery is degraded, the site may load but stories, search, year/month pages, unlocks, or reader navigation may be slow or incomplete.
Payments and token health covers checkout, receipts, token balance, unlock charging, and provider callbacks.
If payment state is uncertain, avoid repeated checkout attempts. Keep receipts and contact support with the time, account email, and payment reference.
Uploads and media health covers images, attachments, static assets, and storage-backed files used by product surfaces.
If uploads/media is degraded, pages may still work while thumbnails, evidence files, uploads, or static media load slowly or fail.
Incident updates should state what is affected, what readers should avoid, and when the next meaningful update is expected.
Useful updates avoid vague reassurance. They identify service, impact, start time, current mitigation, next update, and whether customer action is needed.
If the status page looks wrong, use Support or Contact with the failing URL and account context.
Send exact route, country, device/browser, time, screenshot, account email if relevant, and whether the issue affects reading, login, tokens, upload, or payment.