Announced routes
Every prefix a peer of the route collectors sees with origin AS262868, 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.
| 138.255.196.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 164.163.148.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 168.197.212.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 168.227.72.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.20.208.0/20 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.20.213.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 138.255.196.0/23 | Valid | Other IRR onlyTC | 670 100% |
| 138.255.198.0/23 | Valid | Other IRR onlyTC | 670 100% |
| 168.227.72.0/23 | Valid | Other IRR onlyTC | 670 100% |
| 164.163.150.0/23 | Valid | Other IRR onlyTC | 669 99% |
| 177.20.215.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 177.20.216.0/21 | Valid | Other IRR onlyTC | 669 99% |
| 164.163.148.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 168.197.212.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 168.197.214.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 168.227.74.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 177.20.208.0/21 | Valid | Other IRR onlyTC | 668 99% |
| 2804:328::/33 | Valid | Other IRR onlyTC | 636 100% |
| 2804:328:8000::/33 | Valid | Other IRR onlyTC | 636 100% |
| 2804:328::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS262868: AS262868:AS-ITNETTELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262868 isn't in the set, or no route object for AS262868 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS262868 in it | Not covered |
|---|---|---|---|---|---|
| AS262868:AS-ITNETTELECOM | TC | 4 | 3 | Yes | 0 |
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.
- Route object: RIR20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.255.196.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.148.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.212.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.227.72.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.20.208.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.20.213.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.196.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.198.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.227.72.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.150.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.20.215.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.20.216.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 164.163.148.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.212.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.214.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.227.74.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.20.208.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:328::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:328:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:328::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS262868 is announced.
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.