Network · data from 2026-11-12
AS268697 AS268697 - I A TORRES PROVEDORES ME
Registry name: AS268697 - I A TORRES PROVEDORES ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268697, 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.165.250.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 45.165.251.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 45.165.248.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 2804:5538::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:5538::/33 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:5538::/34 | Valid | Other IRR onlyTC | 632 99% |
| 2804:5538:4000::/34 | Valid | Other IRR onlyTC | 632 99% |
| 2804:5538:8000::/33 | Valid | Other IRR onlyTC | 632 99% |
| 2804:5538:8000::/34 | Valid | Other IRR onlyTC | 632 99% |
| 2804:5538:c000::/34 | Valid | Other IRR onlyTC | 632 99% |
| 45.165.248.0/24 | Valid | Other IRR onlyTC | 19 3%low visibility |
| 45.165.249.0/24 | Valid | Other IRR onlyTC | 19 3%low visibility |
AS-SET
AS268697 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 14 are in fix.csv.
- Route object: RIR12
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.165.250.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.251.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.248.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5538:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.248.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.165.249.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268697 whose prefix no peer sees AS268697 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.165.248.0/22 | RADB, TC | Valid |
| 45.165.250.0/23 | TC | 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.