Network · data from 2026-11-12
AS270483 INFOTECHNET
Registry name: AS270483 - OVERNET FIBRA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270483, 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.
| 200.73.216.0/23 | Valid | Nonecovered by 200.73.216.0/22 | 670 100% |
| 200.73.218.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 200.73.216.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 672 100% |
| 200.73.216.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.73.217.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.73.219.0/24 | Valid | Other IRR onlyRADB | 665 99% |
| 2804:6ca8::/32 | Valid | Other IRR onlyNTTCOM, RADB, TC | 630 99% |
| 2804:6ca8:8f00::/40 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS270483: AS270483. 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 (AS270483 isn't in the set, or no route object for AS270483 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 | AS270483 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS270483 | A single AS number, not a set: AS270483 (this network), 7 route objects. | |||||
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 8 are in fix.csv.
- Route object: none1
- Route object: RIR7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.73.216.0/23 | No route object for it. A route object for 200.73.216.0/22 with origin AS270483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270483 in the RIR database for the space. |
| Route object: RIR | 200.73.218.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.216.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.73.219.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6ca8::/32 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6ca8:8f00::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS270483 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.