bgpreport

Network · data from 2026-11-12

AS266061 Radio Gaga Internet e Serviços

Registry name: AS266061 - Radio Gaga Internet e Servicos Ltda, BR · PeeringDB

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

Announced routes

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

186.209.104.0/24 Valid Other origin only 672 100% 67
186.209.105.0/24 Valid Other origin only 672 100% 67
45.4.212.0/22 Valid Other IRR onlyRADB, TC 665 99% 67
2804:39f4::/32 Valid Other IRR onlyRADB, TC 629 99% 67

AS-SET

AS266061'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 4 are in fix.csv.

  • Route object: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none186.209.104.0/24Route objects for it name AS53153. Add a route object with origin AS266061 in the RIR database for the space.672 of 673
Route object: none186.209.105.0/24Route objects for it name AS53153. Add a route object with origin AS266061 in the RIR database for the space.672 of 673
Route object: RIR45.4.212.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:39f4::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636

Route objects not announced

Every route object with origin AS266061 is announced.

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.