bgpreport

Network · data from 2026-11-12

AS267372 TRINDADEWEB PROVEDOR

Registry name: AS267372 - TRINDADEWEB PROVEDOR, BR · PeeringDB

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

Announced routes

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

45.233.175.0/24 No ROA Nonecovered by 45.233.174.0/23 668 99% 67
45.233.174.0/24 No ROA Nonecovered by 45.233.174.0/23 667 99% 67
2804:4c78::/33 No ROA Nonecovered by 2804:4c78::/32 1 0%low visibility 1
2804:4c78:8000::/33 No ROA Nonecovered by 2804:4c78::/32 1 0%low visibility 1
45.233.174.0/23 No ROA Other IRR onlyRADB 671 100% 67
45.233.172.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.233.173.0/24 No ROA Other IRR onlyRADB 669 99% 67
2804:4c78::/32 No ROA Other IRR onlyALTDB, RADB, TC 635 100% 67

AS-SET

AS267372's PeeringDB record names no AS-SET.

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.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.233.175.0/24No ROA covers it. Add a ROA for AS267372, maxLength 24.668 of 673
Route object: none45.233.175.0/24No route object for it. A route object for 45.233.174.0/23 with origin AS267372 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267372 in the RIR database for the space.668 of 673
ROA: none45.233.174.0/24No ROA covers it. Add a ROA for AS267372, maxLength 24.667 of 673
Route object: none45.233.174.0/24No route object for it. A route object for 45.233.174.0/23 with origin AS267372 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267372 in the RIR database for the space.667 of 673
ROA: none2804:4c78::/33No ROA covers it. Add a ROA for AS267372, maxLength 33.1 of 636
Route object: none2804:4c78::/33No route object for it. A route object for 2804:4c78::/32 with origin AS267372 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267372 in the RIR database for the space.1 of 636
ROA: none2804:4c78:8000::/33No ROA covers it. Add a ROA for AS267372, maxLength 33.1 of 636
Route object: none2804:4c78:8000::/33No route object for it. A route object for 2804:4c78::/32 with origin AS267372 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267372 in the RIR database for the space.1 of 636
ROA: none45.233.174.0/23No ROA covers it. Add a ROA for AS267372, maxLength 23.671 of 673
Route object: RIR45.233.174.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.233.172.0/24No ROA covers it. Add a ROA for AS267372, maxLength 24.670 of 673
Route object: RIR45.233.172.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.233.173.0/24No ROA covers it. Add a ROA for AS267372, maxLength 24.669 of 673
Route object: RIR45.233.173.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:4c78::/32No ROA covers it. Add a ROA for AS267372, maxLength 32.635 of 636
Route object: RIR2804:4c78::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.233.172.0/22ALTDB, RADB, 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.