Network · data from 2026-11-12
AS264406 Staff Computer
Registry name: AS264406 - ContilNet Telecom - Staff Computer EIRELI, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264406, 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.
| 131.221.84.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 143.202.40.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 131.221.87.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 143.202.40.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 143.202.41.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 143.202.42.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 131.221.85.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 143.202.43.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 131.221.84.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 131.221.86.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 2804:1e08::/32 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS264406: AS264406:AS-264406. 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 (AS264406 isn't in the set, or no route object for AS264406 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 | AS264406 in it | Not covered |
|---|---|---|---|---|---|
| AS264406:AS-264406 | TC1 member set in no database: AS264406:AS-CUSTUMERS | 1 | 1 | 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 18 are in fix.csv.
- Route object: RIR11
- AS-SET: missing member1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 131.221.84.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.40.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.221.87.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.40.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.41.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.42.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.221.85.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.43.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.221.84.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.221.86.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1e08::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS264406:AS-264406 | AS264406:AS-264406 (TC) lists AS264406:AS-CUSTUMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS264406 whose prefix no peer sees AS264406 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.221.84.0/23 | RADB | Valid |
| 131.221.86.0/23 | RADB | Valid |
| 143.202.40.0/23 | RADB | Valid |
| 143.202.42.0/23 | RADB | Valid |
| 2804:1e08::/33 | RADB | Valid |
| 2804:1e08:8000::/33 | RADB | 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.