bgpreport

Network · data from 2026-11-12

AS45178 ROSHAN-AF - Main Street, House No. 13 Wazir Akbar Khan

Registry name: ROSHAN-AF - Main Street, House No. 13 Wazir Akbar Khan, AF · not in PeeringDB

30IPv4 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
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS45178, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45178, 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.
64.207.208.0/24 Valid RIR databaseAPNIC 673 100% 66
64.207.214.0/24 Valid RIR databaseAPNIC 673 100% 67
103.28.132.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.28.134.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.112.164.0/24 Valid RIR databaseAPNIC 673 100% 66
103.112.165.0/24 Valid RIR databaseAPNIC 673 100% 66
103.112.166.0/24 Valid RIR databaseAPNIC 673 100% 66
103.112.167.0/24 Valid RIR databaseAPNIC 673 100% 66
111.125.152.0/24 Valid RIR databaseAPNIC 673 100% 66
111.125.153.0/24 Valid RIR databaseAPNIC 673 100% 66
111.125.154.0/24 Valid RIR databaseAPNIC 673 100% 66
111.125.155.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
111.125.157.0/24 Valid RIR databaseAPNIC 673 100% 67
111.125.158.0/24 Valid RIR databaseAPNIC 673 100% 66
116.206.188.0/24 Valid RIR databaseAPNIC 673 100% 66
116.206.189.0/24 Valid RIR databaseAPNIC 673 100% 66
116.206.190.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
64.207.209.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
64.207.212.0/24 Valid RIR databaseAPNIC 672 100% 66
64.207.213.0/24 Valid RIR databaseAPNIC 672 100% 66
64.207.215.0/24 Valid RIR databaseAPNIC 672 100% 67
74.118.80.0/24 Valid RIR databaseAPNIC 672 100% 67
74.118.81.0/24 Valid RIR databaseAPNIC 672 100% 67
103.28.135.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
111.125.156.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
111.125.159.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.174.27.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
74.118.82.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
74.118.83.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.28.133.0/24 Valid RIR databaseAPNIC, RADB 670 100% 66

AS-SET

AS45178 isn't in PeeringDB, where networks name their 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 20 are in fix.csv.

  • Route object: not announced20

Route objects not announced

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

64.207.208.0/21APNICValid
64.207.208.0/22APNICValid
64.207.208.0/23APNICValid
64.207.210.0/23APNICValid
64.207.210.0/24APNICValid
64.207.211.0/24APNICValid
64.207.212.0/23APNICValid
64.207.214.0/23APNICValid
74.118.80.0/22APNICValid
74.118.80.0/23APNICValid
74.118.82.0/23APNICValid
86.96.120.0/24RIPEInvalid: origin
103.28.132.0/22APNICValid
103.28.132.0/23APNIC, RADBValid
103.28.134.0/23APNIC, RADBValid
103.112.164.0/22APNICValid
111.125.152.0/21APNICValid
111.125.152.0/22APNICValid
111.125.152.0/23APNIC, RADBValid
2406:d100::/32APNICValid

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.