bgpreport

Network · data from 2026-11-12

AS266355 Sulnet Telecom

Registry name: AS266355 - SULNET TELECOMUNICACOES LTDA, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
10IPv6 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
12Route objects not announced registered with origin AS266355, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266355, 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.
170.239.106.0/23 Valid Other IRR onlyRADB 668 99% 66
170.239.106.0/24 Valid Other IRR onlyRADB 667 99% 66
170.239.107.0/24 Valid Other IRR onlyRADB 667 99% 66
170.239.104.0/23 Valid Other IRR onlyRADB 666 99% 67
2804:368c::/33 Valid Other IRR onlyRADB 635 100% 68
2804:368c:8000::/33 Valid Other IRR onlyRADB 632 99% 67
2804:368c:8000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:9000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:a000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:b000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:c000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:d000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:e000::/36 Valid Other IRR onlyRADB 632 99% 67
2804:368c:f000::/36 Valid Other IRR onlyRADB 632 99% 67

AS-SET

AS266355'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 26 are in fix.csv.

  • Route object: RIR14
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: RIR170.239.106.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.239.106.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.239.107.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR170.239.104.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:368c::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:368c:8000::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:8000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:9000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:a000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:b000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:c000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:d000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:e000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:368c:f000::/36Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

170.239.104.0/22ALTDB, RADB, TCNo ROA
170.239.104.0/24RADBValid
170.239.105.0/24RADBValid
2804:368c::/32ALTDB, RADB, TCNo ROA
2804:368c::/34RADBValid
2804:368c::/36RADBValid
2804:368c:6000::/35RADBValid
2804:368c:6000::/36RADBValid
2804:368c:7000::/36RADBValid
2804:368c:fc00::/38RADBValid
2804:368c:fc00::/39RADBValid
2804:368c:fe00::/39RADBValid

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.