Network · data from 2026-11-12
AS45905 Stargate Communications
Registry name: STARGATE-AS-AP - Stargate Communications Ltd., BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45905, 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.
| 160.22.151.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.59.36.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.59.37.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.59.38.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.59.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.96.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 119.15.157.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 123.253.196.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 123.253.215.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.22.150.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.148.208.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.148.209.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.148.210.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.148.215.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 45.126.74.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.65.134.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.65.135.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.77.100.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.96.36.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.96.37.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.96.38.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 116.212.185.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 123.253.198.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 123.253.199.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.148.211.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.148.212.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.148.213.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 180.148.214.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.118.244.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.118.245.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.118.246.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 45.126.75.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 119.15.156.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2405:86c0::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 123.253.197.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 45.118.247.0/24 | Valid | RIR databaseAPNIC | 0 0%low visibility |
AS-SET
AS45905'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 52 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced50
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 160.22.151.0/24 | ROAs covering it name AS150774, not AS45905. If AS45905 should announce it, add a ROA for AS45905. |
| Route object: none | 160.22.151.0/24 | Route objects for it name AS150774. Add a route object with origin AS45905 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45905 whose prefix no peer sees AS45905 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.118.244.0/22 | APNIC | Valid |
| 45.118.244.0/23 | APNIC | Valid |
| 45.118.246.0/23 | APNIC | Valid |
| 45.126.74.0/23 | APNIC | Valid |
| 103.59.36.0/22 | APNIC | Valid |
| 103.59.36.0/23 | APNIC | Valid |
| 103.59.38.0/23 | APNIC | Valid |
| 103.65.134.0/23 | APNIC | Valid |
| 103.96.36.0/22 | APNIC | Valid |
| 103.96.36.0/23 | APNIC | Valid |
| 103.96.38.0/23 | APNIC | Valid |
| 119.15.158.0/24 | APNIC | Valid |
| 119.15.159.0/24 | APNIC | Valid |
| 180.148.208.0/21 | APNIC | Valid |
| 180.148.208.0/22 | APNIC | Valid |
| 180.148.208.0/23 | APNIC | Valid |
| 180.148.210.0/23 | APNIC | Valid |
| 180.148.212.0/22 | APNIC | Valid |
| 180.148.212.0/23 | APNIC | Valid |
| 180.148.214.0/23 | APNIC | Valid |
| 2405:86c0::/33 | APNIC | Valid |
| 2405:86c0::/34 | APNIC | Valid |
| 2405:86c0::/35 | APNIC | Valid |
| 2405:86c0::/36 | APNIC | Valid |
| 2405:86c0:1000::/36 | APNIC | Valid |
| 2405:86c0:2000::/35 | APNIC | Valid |
| 2405:86c0:2000::/36 | APNIC | Valid |
| 2405:86c0:3000::/36 | APNIC | Valid |
| 2405:86c0:4000::/34 | APNIC | Valid |
| 2405:86c0:4000::/35 | APNIC | Valid |
| 2405:86c0:4000::/36 | APNIC | Valid |
| 2405:86c0:5000::/36 | APNIC | Valid |
| 2405:86c0:6000::/35 | APNIC | Valid |
| 2405:86c0:6000::/36 | APNIC | Valid |
| 2405:86c0:7000::/36 | APNIC | Valid |
| 2405:86c0:8000::/33 | APNIC | Valid |
| 2405:86c0:8000::/34 | APNIC | Valid |
| 2405:86c0:8000::/35 | APNIC | Valid |
| 2405:86c0:8000::/36 | APNIC | Valid |
| 2405:86c0:9000::/36 | APNIC | Valid |
| 2405:86c0:a000::/35 | APNIC | Valid |
| 2405:86c0:a000::/36 | APNIC | Valid |
| 2405:86c0:b000::/36 | APNIC | Valid |
| 2405:86c0:c000::/34 | APNIC | Valid |
| 2405:86c0:c000::/35 | APNIC | Valid |
| 2405:86c0:c000::/36 | APNIC | Valid |
| 2405:86c0:d000::/36 | APNIC | Valid |
| 2405:86c0:e000::/35 | APNIC | Valid |
| 2405:86c0:e000::/36 | APNIC | Valid |
| 2405:86c0:f000::/36 | APNIC | Valid |
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.