bgpreport

Network · data from 2026-11-12

AS264233 WF -TELECOM SERVIOS DE TELECOMUNICAOES EIRELE ME

Registry name: AS264233 - WF -TELECOM SERVICOS DE TELECOMUNICACOES EIRELE ME, BR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS264233, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264233, 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.
138.117.116.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
138.117.116.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
138.117.116.0/24 Valid Other IRR onlyTC 671 100% 67
138.117.117.0/24 Valid Other IRR onlyTC 671 100% 67
138.117.118.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
170.80.100.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
170.80.100.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
170.80.101.0/24 Valid Other IRR onlyTC 671 100% 67
170.80.102.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
138.117.118.0/24 Valid Other IRR onlyTC 670 100% 67
138.117.119.0/24 Valid Other IRR onlyTC 670 100% 67
170.80.100.0/24 Valid Other IRR onlyTC 670 100% 67
170.80.102.0/24 Valid Other IRR onlyTC 670 100% 67
170.80.103.0/24 Valid Other IRR onlyTC 670 100% 67
2804:249c::/33 Valid Other IRR onlyRADB, TC 635 100% 67
2804:249c:8000::/33 Valid Other IRR onlyRADB, TC 635 100% 67
2804:249c::/32 Valid Other IRR onlyRADB, TC 633 100% 68

AS-SET

AS264233'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.

  • Route object: RIR17
ChangePrefix or setDetailFull-table peers
Route object: RIR138.117.116.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.116.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.116.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.117.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.118.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.80.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.80.100.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.80.101.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.80.102.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.118.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR138.117.119.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.80.100.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.80.102.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.80.103.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:249c::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:249c:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:249c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS264233 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.