Renewal History
railway.app
railway.app has been renewed 4 times, usually 1 year at a time, about 7 months before expiry. The longest single renewal was 2 years, around 2025, out to 2028. No near-death on record.
Every renewal, newest first
- 2025between Jul 12, 2025 and Aug 12, 2025+2 yearsexpiry Aug 1, 2026 → Aug 1, 2028Early12 to 13 months before expiryRegistry confirmed an explicit renewal
- 2025between Apr 15, 2025 and Jul 12, 2025+1 yearexpiry Aug 1, 2025 → Aug 1, 2026Early1 to 4 months before expiry
- 2024between Jun 23, 2024 and Jul 8, 2024+1 yearexpiry Aug 1, 2024 → Aug 1, 2025Early3 to 6 weeks before expiry
- 2023between Jun 14, 2023 and Aug 7, 2023+1 yearexpiry Aug 1, 2023 → Aug 1, 2024Around expirysnapshots too far apart to say how early
How this is worked out. Each renewal is a forward jump in the registry’s expiry date between two WHOIS or RDAP snapshots. The size of the jump is the number of years paid for. The renewal happened somewhere between the two snapshot dates, so how early or late it was is a range; when the snapshots are far apart, it is not stated.
For .com and .net the registry itself extends the expiry on the day it lapses and gives the registrar 45 days to pay or delete, so a jump right at expiry is not proof the owner paid. The ledger marks renewals the registry flagged as explicit, and near-deaths where it later showed a redemption or pending-delete status.
Source: 114 snapshots of railway.app from the who.is WHOIS/RDAP archive, 2022-10-09 to 2026-05-19. Ledger built 2026-09-27.