bgpreport

Network · data from 2026-11-12

AS263627 Wnetsistem Comercio e Servicos de Informatica Ltda

Registry name: AS263627 - Wnetsistem Comercio e Servicos de Informatica Ltda, BR · PeeringDB

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

Announced routes

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

177.12.95.0/24 Invalid: maxLength Nonecovered by 177.12.92.0/22 60 9%low visibility 30
143.202.236.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
170.80.0.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
177.12.92.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
143.202.236.0/24 Valid Other IRR onlyRADB 666 99% 66
143.202.237.0/24 Valid Other IRR onlyRADB 666 99% 66
143.202.238.0/24 Valid Other IRR onlyRADB 666 99% 66
143.202.239.0/24 Valid Other IRR onlyRADB 666 99% 66
170.80.0.0/24 Valid Other IRR onlyRADB 666 99% 66
170.80.1.0/24 Valid Other IRR onlyRADB 666 99% 66
170.80.2.0/24 Valid Other IRR onlyRADB 666 99% 66
170.80.3.0/24 Valid Other IRR onlyRADB 666 99% 66
177.12.92.0/24 Valid Other IRR onlyRADB 666 99% 66
177.12.93.0/24 Valid Other IRR onlyRADB 666 99% 66
177.12.94.0/24 Valid Other IRR onlyRADB 666 99% 66
2804:1044::/32 Valid Other IRR onlyRADB, TC 634 100% 69
2804:1044::/33 Valid Other IRR onlyRADB 634 100% 69
2804:1044::/34 Valid Other IRR onlyRADB 634 100% 69
2804:1044:4000::/34 Valid Other IRR onlyRADB 634 100% 69
2804:1044:8000::/33 Valid Other IRR onlyRADB 634 100% 69
2804:1044:8000::/34 Valid Other IRR onlyRADB 634 100% 69
2804:1044:c000::/34 Valid Other IRR onlyRADB 634 100% 69

AS-SET

AS263627'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 23 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
ROA: maxLength177.12.95.0/24ROA 177.12.92.0/22 AS263627 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 177.12.95.0/24.60 of 673
Route object: none177.12.95.0/24No route object for it. A route object for 177.12.92.0/22 with origin AS263627 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263627 in the RIR database for the space.60 of 673
Route object: RIR143.202.236.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.80.0.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.12.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR143.202.236.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR143.202.237.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR143.202.238.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR143.202.239.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR170.80.0.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR170.80.1.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR170.80.2.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR170.80.3.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.12.92.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.12.93.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.12.94.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:1044::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044:4000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044:8000::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1044:c000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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