bgpreport

Network · data from 2026-11-12

AS266296 Green Telecom LTDA

Registry name: AS266296 - Green Telecom LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266296, 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.
170.79.94.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.79.95.0/24 Valid Other IRR onlyALTDB, RADB, TC 671 100% 66
170.79.92.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
170.79.93.0/24 Valid Other IRR onlyTC 670 100% 67
2804:359c:2400::/38 Valid Other IRR onlyTC 635 100% 67
2804:359c:9000::/38 Valid Other IRR onlyTC 635 100% 67
2804:359c:9000::/39 Valid Other IRR onlyTC 2 0%low visibility 2
2804:359c:9200::/39 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

AS266296'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 12 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR170.79.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.79.95.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.79.92.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.79.93.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:359c:2400::/38Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:359c:9000::/38Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:359c:9000::/39Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:359c:9200::/39Route object only in TC. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

170.79.92.0/22ALTDB, RADB, TCNo ROA
2804:359c::/32ALTDB, RADB, TCNo ROA
2804:359c:2400::/39TCValid
2804:359c:2600::/39TCValid

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.