Network · data from 2026-11-12
AS274992 AS274992 - LAR62
Registry name: AS274992 - LAR62, EC · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS274992, 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.
| 2803:7d30:116::/48 | Valid | Nonecovered by 2803:7d30:100::/40 | 632 99% |
AS-SET
AS274992 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 | 2803:7d30:116::/48 | No route object for it. A route object for 2803:7d30:100::/40 with origin AS274992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274992 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS274992 whose prefix no peer sees AS274992 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:7d30::/32 | LACNIC, RADB | Valid |
| 2803:7d30:100::/40 | LACNIC | Valid |
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.