bgpreport

Network · data from 2026-11-12

AS269809 AS269809 - ESTRELLA JORGE ALBERTO (GLOBALWIFI)

Registry name: AS269809 - ESTRELLA JORGE ALBERTO (GLOBALWIFI), AR · not in PeeringDB

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

Announced routes

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

2803:c4e0:1000::/45 Valid Nonecovered by 2803:c4e0:1000::/36 632 99% 69
2803:c4e0:1008::/45 Valid Nonecovered by 2803:c4e0:1000::/36 632 99% 69
2803:c4e0:1010::/45 Valid Nonecovered by 2803:c4e0:1000::/36 632 99% 69
2803:c4e0:1018::/45 Valid Nonecovered by 2803:c4e0:1000::/36 632 99% 69
45.191.5.0/24 Valid RIR databaseLACNIC 673 100% 66
45.191.6.0/24 Valid RIR databaseLACNIC 673 100% 66
45.191.7.0/24 Valid RIR databaseLACNIC 673 100% 66
45.191.4.0/24 Valid RIR databaseLACNIC 672 100% 66
2803:c4e0::/36 Valid RIR databaseLACNIC 633 100% 69
2803:c4e0:8000::/36 Valid RIR databaseLACNIC 633 100% 69

AS-SET

AS269809 isn't in PeeringDB, where networks name their 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 19 are in fix.csv.

  • Route object: none4
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2803:c4e0:1000::/45No route object for it. A route object for 2803:c4e0:1000::/36 with origin AS269809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269809 in the RIR database for the space.632 of 636
Route object: none2803:c4e0:1008::/45No route object for it. A route object for 2803:c4e0:1000::/36 with origin AS269809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269809 in the RIR database for the space.632 of 636
Route object: none2803:c4e0:1010::/45No route object for it. A route object for 2803:c4e0:1000::/36 with origin AS269809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269809 in the RIR database for the space.632 of 636
Route object: none2803:c4e0:1018::/45No route object for it. A route object for 2803:c4e0:1000::/36 with origin AS269809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269809 in the RIR database for the space.632 of 636

Route objects not announced

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

2803:c4e0::/32LACNICValid
2803:c4e0:1000::/36LACNICValid
2803:c4e0:2000::/36LACNICValid
2803:c4e0:3000::/36LACNICValid
2803:c4e0:4000::/36LACNICValid
2803:c4e0:5000::/36LACNICValid
2803:c4e0:6000::/36LACNICValid
2803:c4e0:7000::/36LACNICValid
2803:c4e0:9000::/36LACNICValid
2803:c4e0:a000::/36LACNICValid
2803:c4e0:b000::/36LACNICValid
2803:c4e0:c000::/36LACNICValid
2803:c4e0:d000::/36LACNICValid
2803:c4e0:e000::/36LACNICValid
2803:c4e0:f000::/36LACNICValid

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.