Network · data from 2026-11-12
AS7253 MAINSTAY-COMMUNICATIONS - Mainstay Communications
Registry name: MAINSTAY-COMMUNICATIONS - Mainstay Communications, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7253, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 96.46.98.0/24 | Valid | Nonecovered by 96.46.96.0/21 | 671 100% |
| 96.46.96.0/21 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS7253 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 96.46.98.0/24 | No route object for it. A route object for 96.46.96.0/21 with origin AS7253 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7253 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7253 whose prefix no peer sees AS7253 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 96.46.96.0/20 | RADB | No ROA |
| 2606:ac40::/32 | ARIN | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.