bgpreport

Network · data from 2026-11-12

AS268684 PONTO CERTO INTERNET

Registry name: AS268684 - PONTO CERTO INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268684, 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.

2804:5504::/33 No ROA Nonecovered by 2804:5504::/32 352 55% 65
2804:5504:8000::/33 No ROA Nonecovered by 2804:5504::/32 352 55% 65
45.165.172.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
45.165.173.0/24 No ROA Other IRR onlyRADB, TC 672 100% 67
45.165.174.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.165.175.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
45.165.172.0/24 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:5504::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5504:4000::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5504:6000::/40 No ROA Other IRR onlyRADB 635 100% 67
2804:5504:8000::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5504:c000::/34 No ROA Other IRR onlyTC 635 100% 67
2804:5504::/32 No ROA Other IRR onlyRADB, TC 355 56% 65

AS-SET

PeeringDB's irr_as_set for AS268684: AS8684:AS-SET. 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 (AS268684 isn't in the set, or no route object for AS268684 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 objectsAS268684 in itNot covered
AS8684:AS-SET In no IRR database read today.

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 29 are in fix.csv.

  • ROA: none13
  • Route object: none2
  • Route object: RIR11
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:5504::/33No ROA covers it. Add a ROA for AS268684, maxLength 33.352 of 636
Route object: none2804:5504::/33No route object for it. A route object for 2804:5504::/32 with origin AS268684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268684 in the RIR database for the space.352 of 636
ROA: none2804:5504:8000::/33No ROA covers it. Add a ROA for AS268684, maxLength 33.352 of 636
Route object: none2804:5504:8000::/33No route object for it. A route object for 2804:5504::/32 with origin AS268684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268684 in the RIR database for the space.352 of 636
ROA: none45.165.172.0/22No ROA covers it. Add a ROA for AS268684, maxLength 22.672 of 673
Route object: RIR45.165.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.165.173.0/24No ROA covers it. Add a ROA for AS268684, maxLength 24.672 of 673
Route object: RIR45.165.173.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.165.174.0/24No ROA covers it. Add a ROA for AS268684, maxLength 24.672 of 673
Route object: RIR45.165.174.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.165.175.0/24No ROA covers it. Add a ROA for AS268684, maxLength 24.672 of 673
Route object: RIR45.165.175.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none45.165.172.0/24No ROA covers it. Add a ROA for AS268684, maxLength 24.671 of 673
Route object: RIR45.165.172.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:5504::/34No ROA covers it. Add a ROA for AS268684, maxLength 34.635 of 636
Route object: RIR2804:5504::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5504:4000::/34No ROA covers it. Add a ROA for AS268684, maxLength 34.635 of 636
Route object: RIR2804:5504:4000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5504:6000::/40No ROA covers it. Add a ROA for AS268684, maxLength 40.635 of 636
Route object: RIR2804:5504:6000::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:5504:8000::/34No ROA covers it. Add a ROA for AS268684, maxLength 34.635 of 636
Route object: RIR2804:5504:8000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5504:c000::/34No ROA covers it. Add a ROA for AS268684, maxLength 34.635 of 636
Route object: RIR2804:5504:c000::/34Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:5504::/32No ROA covers it. Add a ROA for AS268684, maxLength 32.355 of 636
Route object: RIR2804:5504::/32Route object only in RADB, TC. Add it in the RIR database for the space.355 of 636
AS-SET: not foundAS8684:AS-SETPeeringDB names AS8684:AS-SET; no IRR database read has it.

Route objects not announced

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

45.165.172.0/23RADB, TCNo ROA
45.165.174.0/23RADB, TCNo 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.