bgpreport

Network · data from 2026-11-12

AS266550 WOW TELECOM COMUNICACAO MULTIMIDIA

Registry name: AS266550 - WTD TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266550, 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:3dbc:700::/40 Valid Nonecovered by 2804:3dbc:400::/38 634 100% 67
192.140.65.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
192.140.66.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
192.140.67.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
192.140.64.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:3dbc::/38 Valid Other IRR onlyRADB, TC 636 100% 69
2804:3dbc:c000::/38 Valid Other IRR onlyRADB, TC 636 100% 69

AS-SET

AS266550'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 22 are in fix.csv.

  • Route object: none1
  • Route object: RIR6
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2804:3dbc:700::/40No route object for it. A route object for 2804:3dbc:400::/38 with origin AS266550 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266550 in the RIR database for the space.634 of 636
Route object: RIR192.140.65.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR192.140.66.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR192.140.67.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR192.140.64.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:3dbc::/38Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:3dbc:c000::/38Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

192.140.64.0/22RADB, TCValid
192.140.64.0/23TCValid
192.140.66.0/23RADB, TCValid
2804:24c8::/32RADBNo ROA
2804:3dbc::/32RADB, TCValid
2804:3dbc::/33RADB, TCValid
2804:3dbc::/34RADB, TCValid
2804:3dbc:400::/38RADB, TCValid
2804:3dbc:410::/44RADB, TCValid
2804:3dbc:4000::/34RADB, TCValid
2804:3dbc:8000::/33RADB, TCValid
2804:3dbc:8000::/34RADB, TCValid
2804:3dbc:8000::/35RADB, TCValid
2804:3dbc:c000::/34RADB, TCValid
2804:3dbc:c000::/35RADB, TCValid

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.