Network · data from 2026-11-12
AS266410 BELNET EIRELI
Registry name: AS266410 - BELNET EIRELLI, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266410, 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.80.80.0/23 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 170.80.82.0/23 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:3768::/33 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:3768:8000::/33 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:3768:8000::/34 | Valid | Other IRR onlyRADB, TC | 109 17% |
| 2804:3768:c000::/34 | Valid | Other IRR onlyRADB, TC | 109 17% |
| 170.80.82.0/24 | Valid | Other IRR onlyRADB, TC | 95 14% |
| 170.80.83.0/24 | Valid | Other IRR onlyRADB, TC | 95 14% |
| 170.80.81.0/24 | Valid | Other IRR onlyRADB, TC | 30 4%low visibility |
| 170.80.80.0/24 | Valid | Other IRR onlyRADB, TC | 27 4%low visibility |
AS-SET
PeeringDB's irr_as_set for AS266410: AS266410:AS-ANNOUNCEMENTS. 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 (AS266410 isn't in the set, or no route object for AS266410 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 | AS266410 in it | Not covered |
|---|---|---|---|---|---|
| AS266410:AS-ANNOUNCEMENTS | TC | 2 | 2 | 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 17 are in fix.csv.
- Route object: RIR10
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 170.80.80.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.82.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3768::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3768:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3768:8000::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3768:c000::/34 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.82.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.83.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.81.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.80.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266410 whose prefix no peer sees AS266410 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.80.80.0/22 | RADB, TC | Valid |
| 2804:3768::/32 | RADB, TC | Valid |
| 2804:3768::/34 | RADB, TC | Valid |
| 2804:3768:4000::/34 | RADB, TC | Valid |
| 2804:3768:8000::/41 | RADB | Valid |
| 2804:3768:8080::/41 | RADB | Valid |
| 2804:4d04::/32 | RADB | No ROA |
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.