bgpreport

Network · data from 2026-11-12

AS262693 WCOM COM E SERV TELECOM LTDA

Registry name: AS262693 - WCOM COM E SERV TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262693, 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:32c4:3f::/48 Valid Nonecovered by 2804:32c4::/32 635 100% 67
2804:32c4::/48 Valid Nonecovered by 2804:32c4::/32 631 99% 67
2804:32c4:7f::/48 Valid Nonecovered by 2804:32c4::/32 631 99% 67
187.33.134.0/23 Valid Other IRR onlyRADB 672 100% 67
187.33.142.0/23 Valid Other IRR onlyRADB 672 100% 67
187.33.142.0/24 Valid Other IRR onlyRADB 671 100% 67
187.33.143.0/24 Valid Other IRR onlyRADB 671 100% 67
187.33.129.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.130.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.131.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.132.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.133.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.134.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.135.0/24 Valid Other IRR onlyRADB 670 100% 67
187.33.128.0/24 Valid Other IRR onlyRADB 668 99% 67
187.33.130.0/23 Valid Other IRR onlyRADB 667 99% 67
187.33.141.0/24 Valid Other IRR onlyRADB 665 99% 66
187.33.136.0/24 Valid Other IRR onlyRADB 664 99% 67
187.33.138.0/24 Valid Other IRR onlyRADB 664 99% 67
187.33.140.0/24 Valid Other IRR onlyRADB 663 99% 67

AS-SET

AS262693'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 35 are in fix.csv.

  • Route object: none3
  • Route object: RIR17
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2804:32c4:3f::/48No route object for it. A route object for 2804:32c4::/32 with origin AS262693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262693 in the RIR database for the space.635 of 636
Route object: none2804:32c4::/48No route object for it. A route object for 2804:32c4::/32 with origin AS262693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262693 in the RIR database for the space.631 of 636
Route object: none2804:32c4:7f::/48No route object for it. A route object for 2804:32c4::/32 with origin AS262693 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262693 in the RIR database for the space.631 of 636
Route object: RIR187.33.134.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.33.142.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.33.142.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.33.143.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.33.129.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.130.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.131.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.132.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.133.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.134.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.135.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.33.128.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR187.33.130.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR187.33.141.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR187.33.136.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR187.33.138.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR187.33.140.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673

Route objects not announced

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

187.33.128.0/20RADBValid
187.33.128.0/21RADBValid
187.33.128.0/22RADBValid
187.33.128.0/23RADBValid
187.33.132.0/22RADBValid
187.33.132.0/23RADBValid
187.33.136.0/21RADBValid
187.33.136.0/22RADBValid
187.33.136.0/23RADBValid
187.33.137.0/24RADBValid
187.33.138.0/23RADBValid
187.33.139.0/24RADBValid
187.33.140.0/22RADBValid
187.33.140.0/23RADBValid
2804:32c4::/32RADBValid

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.