Network · data from 2026-11-12
AS268474 L&A Internet
Registry name: AS268474 - L&A Internet, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268474, 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.
| 45.161.205.0/24 | No ROA | Nonecovered by 45.161.204.0/23 | 672 100% |
| 2804:51c0::/33 | No ROA | Nonecovered by 2804:51c0::/32 | 636 100% |
| 2804:51c0::/34 | No ROA | Nonecovered by 2804:51c0::/32 | 636 100% |
| 2804:51c0:4000::/34 | No ROA | Nonecovered by 2804:51c0::/32 | 636 100% |
| 45.161.204.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.161.204.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.161.206.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.161.207.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2804:51c0::/32 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
AS268474's PeeringDB record names no 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 20 are in fix.csv.
- ROA: none9
- Route object: none4
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.161.205.0/24 | No ROA covers it. Add a ROA for AS268474, maxLength 24. |
| Route object: none | 45.161.205.0/24 | No route object for it. A route object for 45.161.204.0/23 with origin AS268474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268474 in the RIR database for the space. |
| ROA: none | 2804:51c0::/33 | No ROA covers it. Add a ROA for AS268474, maxLength 33. |
| Route object: none | 2804:51c0::/33 | No route object for it. A route object for 2804:51c0::/32 with origin AS268474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268474 in the RIR database for the space. |
| ROA: none | 2804:51c0::/34 | No ROA covers it. Add a ROA for AS268474, maxLength 34. |
| Route object: none | 2804:51c0::/34 | No route object for it. A route object for 2804:51c0::/32 with origin AS268474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268474 in the RIR database for the space. |
| ROA: none | 2804:51c0:4000::/34 | No ROA covers it. Add a ROA for AS268474, maxLength 34. |
| Route object: none | 2804:51c0:4000::/34 | No route object for it. A route object for 2804:51c0::/32 with origin AS268474 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268474 in the RIR database for the space. |
| ROA: none | 45.161.204.0/22 | No ROA covers it. Add a ROA for AS268474, maxLength 22. |
| Route object: RIR | 45.161.204.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.161.204.0/24 | No ROA covers it. Add a ROA for AS268474, maxLength 24. |
| Route object: RIR | 45.161.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.161.206.0/24 | No ROA covers it. Add a ROA for AS268474, maxLength 24. |
| Route object: RIR | 45.161.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.161.207.0/24 | No ROA covers it. Add a ROA for AS268474, maxLength 24. |
| Route object: RIR | 45.161.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:51c0::/32 | No ROA covers it. Add a ROA for AS268474, maxLength 32. |
| Route object: RIR | 2804:51c0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268474 whose prefix no peer sees AS268474 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.161.204.0/23 | RADB | No ROA |
| 45.161.206.0/23 | RADB | 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.