bgpreport

Network · data from 2026-11-12

AS262256 Servicios Informáticos Hostname

Registry name: AS262256 - Servicios Informaticos Hostname Ltda, CL · PeeringDB

25IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
20Route objects not announced registered with origin AS262256, seen from no peer

Announced routes

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

45.236.164.0/24 Valid Other IRR onlyRADB 670 100% 68
45.236.165.0/24 Valid Other IRR onlyRADB 670 100% 68
45.236.166.0/24 Valid Other IRR onlyRADB 670 100% 68
190.110.120.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 68
190.110.121.0/24 Valid Other IRR onlyRADB 670 100% 68
190.110.122.0/24 Valid Other IRR onlyRADB 670 100% 68
190.110.123.0/24 Valid Other IRR onlyRADB 670 100% 68
190.110.124.0/24 Valid Other IRR onlyRADB 670 100% 68
190.110.125.0/24 Valid Other IRR onlyRADB 670 100% 68
192.140.56.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
192.140.57.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
192.141.49.0/24 Valid Other IRR onlyRADB 670 100% 68
192.141.50.0/24 Valid Other IRR onlyRADB 670 100% 68
192.141.51.0/24 Valid Other IRR onlyRADB 670 100% 68
200.24.12.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
200.24.13.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
200.24.14.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.169.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.170.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.171.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.173.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.174.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
201.159.175.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 68
190.110.126.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1
200.24.15.0/24 Valid Other IRR onlyNTTCOM, RADB 1 0%low visibility 1

AS-SET

AS262256'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 45 are in fix.csv.

  • Route object: RIR25
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: RIR45.236.164.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.236.165.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.236.166.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.120.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.121.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.122.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.123.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.124.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.125.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.140.56.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.140.57.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.141.49.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.141.50.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.141.51.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.24.12.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.24.13.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.24.14.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.169.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.170.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.171.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.173.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.174.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR201.159.175.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.126.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR200.24.15.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

45.234.164.0/22NTTCOMNo ROA
45.236.164.0/22ALTDB, LACNIC, RADBValid
45.236.167.0/24RADBValid
170.82.128.0/22RADBNo ROA
170.82.128.0/24RADBNo ROA
170.82.129.0/24RADBNo ROA
170.82.130.0/24RADBNo ROA
170.82.131.0/24RADBNo ROA
190.110.120.0/21NTTCOM, RADBValid
190.110.127.0/24RADBValid
192.140.56.0/22ALTDB, LACNIC, NTTCOM, RADBValid
192.140.58.0/24NTTCOM, RADBValid
192.140.59.0/24NTTCOM, RADBValid
192.141.48.0/22NTTCOM, RADBValid
192.141.48.0/24RADBValid
200.24.12.0/22ALTDB, NTTCOM, RADBValid
201.159.168.0/21ALTDB, NTTCOM, RADBValid
201.159.168.0/24NTTCOM, RADBValid
201.159.172.0/24NTTCOM, RADBValid
2803:a2c0::/32RADBNo ROA

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.