How we work

Data status

Status pages, releases and company posts are checked automatically. Resets, announcements and limit changes from official accounts publish themselves, marked as published automatically, and an editor checks them afterwards. Outages and program news are reviewed by an editor first. The reset history since 2025 comes from posts by the companies and their staff on X: text and time were checked against the source, and every record links to it. When a program’s official page changes, the change shows on the program page right away.

Event types

An announcement and its confirmation form one episode. Two posts about the same reset do not increase the count. A banked reset (granted, activated manually) is counted separately from a limit restore.

Dates and time

Source dates are stored in UTC. If the applied time is unknown, the calendar uses the clearly marked publication time. Changing the time zone in settings can move an event to another calendar day.

Statistics

The median is published once there are five full gaps. Only confirmed resets are included. Gaps are counted per company. The share of advance announcements refers only to the observed history. There are no forecasts of the next reset.

Credits

Direct API, cloud platform and subscription balances are separate. Unknown terms are not treated as met. The eligibility check does not mean the application will be approved.

How hard to get

An estimate based on the published requirements, not an approval probability. Low: verifying your status is enough. Medium: a regular application, sometimes via a partner. High: requires investment, another program membership or reaching a company representative.

Region

The region in settings is separate from the language. If a program's terms name specific countries and your region differs, the card says so.

Corrections

Cancellations and clarifications are added to the history. Changes are listed in the changelog.