bgpreport

Network · data from 2026-11-12

AS271181 Whnet Telecom Servicos de Telecomunicacoes LTDA

Registry name: AS271181 - whnet telecom servicos de telecomunicacoes 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
6Route objects not announced registered with origin AS271181, seen from no peer

Announced routes

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

190.107.92.0/24 Valid Other IRR onlyTC 669 99% 67
190.107.94.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
190.107.95.0/24 Valid Other IRR onlyRADB, TC 666 99% 66
190.107.93.0/24 Valid Other IRR onlyTC 665 99% 67
2804:777c::/33 Valid Other IRR onlyTC 635 100% 67
2804:777c:8000::/33 Valid Other IRR onlyRADB, TC 631 99% 67
2804:777c::/34 Valid Other IRR onlyTC 48 8%low visibility 29
2804:777c:4000::/34 Valid Other IRR onlyTC 48 8%low visibility 29

AS-SET

AS271181'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 14 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR190.107.92.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR190.107.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR190.107.95.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR190.107.93.0/24Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:777c::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:777c:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:777c::/34Route object only in TC. Add it in the RIR database for the space.48 of 636
Route object: RIR2804:777c:4000::/34Route object only in TC. Add it in the RIR database for the space.48 of 636

Route objects not announced

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

190.107.92.0/22RADB, TCValid
190.107.92.0/23RADB, TCValid
190.107.94.0/23TCValid
2804:777c::/32RADB, TCValid
2804:777c:8000::/34TCValid
2804:777c:c000::/34TCValid

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.