Network · data from 2026-11-12
AS266015 AS266015 - ALL FAST NETWORK LTDA
Registry name: AS266015 - ALL FAST NETWORK LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266015, 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.
| 170.245.76.0/23 | Valid | Nonecovered by 170.245.76.0/22 | 670 100% |
| 2804:3928::/33 | Valid | Nonecovered by 2804:3928::/32 | 635 100% |
| 2804:3928:100::/40 | Valid | Nonecovered by 2804:3928::/34 | 634 100% |
| 170.245.76.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 170.245.77.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 170.245.78.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 170.245.79.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 2804:3928:c000::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:3928:8000::/34 | Valid | Other IRR onlyTC | 633 100% |
AS-SET
AS266015 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 13 are in fix.csv.
- Route object: none3
- Route object: RIR6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.245.76.0/23 | No route object for it. A route object for 170.245.76.0/22 with origin AS266015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266015 in the RIR database for the space. |
| Route object: none | 2804:3928::/33 | No route object for it. A route object for 2804:3928::/32 with origin AS266015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266015 in the RIR database for the space. |
| Route object: none | 2804:3928:100::/40 | No route object for it. A route object for 2804:3928::/34 with origin AS266015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266015 in the RIR database for the space. |
| Route object: RIR | 170.245.76.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.77.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.78.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.79.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3928:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3928:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266015 whose prefix no peer sees AS266015 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.245.76.0/22 | RADB, TC | No ROA |
| 2804:3928::/32 | RADB, TC | No ROA |
| 2804:3928::/34 | TC | Valid |
| 2804:3928:4000::/34 | 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.