bgpreport

Network · data from 2026-11-12

AS266374 Ponte Digital

Registry name: AS266374 - Ponte Digital, BR · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS266374, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266374, 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.48.0/22 No ROA Other IRR onlyALTDB, RADB, TC 671 100% 66
2804:36d0::/32 No ROA Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:36d0::/33 No ROA Other IRR onlyTC 635 100% 67
2804:36d0:8000::/33 No ROA Other IRR onlyTC 635 100% 67
170.80.48.0/23 No ROA Other IRR onlyTC 201 30% 54
170.80.50.0/23 No ROA Other IRR onlyTC 201 30% 54

AS-SET

PeeringDB's irr_as_set for AS266374: AS266374:AS-ALL. 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 (AS266374 isn't in the set, or no route object for AS266374 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.

NameDatabaseASNsSets Route objectsAS266374 in itNot covered
AS266374:AS-ALL ALTDB 1110 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none170.80.48.0/22No ROA covers it. Add a ROA for AS266374, maxLength 22.671 of 673
Route object: RIR170.80.48.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:36d0::/32No ROA covers it. Add a ROA for AS266374, maxLength 32.635 of 636
Route object: RIR2804:36d0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:36d0::/33No ROA covers it. Add a ROA for AS266374, maxLength 33.635 of 636
Route object: RIR2804:36d0::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:36d0:8000::/33No ROA covers it. Add a ROA for AS266374, maxLength 33.635 of 636
Route object: RIR2804:36d0:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none170.80.48.0/23No ROA covers it. Add a ROA for AS266374, maxLength 23.201 of 673
Route object: RIR170.80.48.0/23Route object only in TC. Add it in the RIR database for the space.201 of 673
ROA: none170.80.50.0/23No ROA covers it. Add a ROA for AS266374, maxLength 23.201 of 673
Route object: RIR170.80.50.0/23Route object only in TC. Add it in the RIR database for the space.201 of 673

Route objects not announced

Route objects with origin AS266374 whose prefix no peer sees AS266374 announce. Many are kept on purpose (backup routes, space announced only in some places).

170.80.48.0/24TCNo ROA
170.80.49.0/24TCNo ROA
170.80.50.0/24TCNo ROA
170.80.51.0/24TCNo 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.