bgpreport

Network · data from 2026-11-12

AS269369 WHD Fibra

Registry name: AS269369 - WHD Internet, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269369, 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:6390::/36 No ROA Nonecovered by 2804:6390::/32 630 99% 67
2804:6390:f000::/36 No ROA Nonecovered by 2804:6390::/32 630 99% 67
45.185.8.0/23 No ROA Other IRR onlyRADB 671 100% 66
45.185.8.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.185.9.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.185.11.0/24 No ROA Other IRR onlyRADB 671 100% 66

AS-SET

AS269369'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 16 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:6390::/36No ROA covers it. Add a ROA for AS269369, maxLength 36.630 of 636
Route object: none2804:6390::/36No route object for it. A route object for 2804:6390::/32 with origin AS269369 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269369 in the RIR database for the space.630 of 636
ROA: none2804:6390:f000::/36No ROA covers it. Add a ROA for AS269369, maxLength 36.630 of 636
Route object: none2804:6390:f000::/36No route object for it. A route object for 2804:6390::/32 with origin AS269369 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269369 in the RIR database for the space.630 of 636
ROA: none45.185.8.0/23No ROA covers it. Add a ROA for AS269369, maxLength 23.671 of 673
Route object: RIR45.185.8.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.185.8.0/24No ROA covers it. Add a ROA for AS269369, maxLength 24.671 of 673
Route object: RIR45.185.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.185.9.0/24No ROA covers it. Add a ROA for AS269369, maxLength 24.671 of 673
Route object: RIR45.185.9.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.185.11.0/24No ROA covers it. Add a ROA for AS269369, maxLength 24.671 of 673
Route object: RIR45.185.11.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

45.185.8.0/22TCNo ROA
45.185.10.0/23RADBNo ROA
45.185.10.0/24RADBNo ROA
2804:6390::/32TCNo 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.