Network · data from 2026-11-12
AS150180 AFRENIT-AS-AP - AFREN IT
Registry name: AFRENIT-AS-AP - AFREN IT, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150180, 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.
| 103.37.185.0/24 | Valid | Other origin onlycovered by 103.37.184.0/23 | 672 100% |
| 202.50.155.0/24 | Valid | Other origin only | 672 100% |
| 103.209.92.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 123.0.28.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 157.20.74.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 160.30.176.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 160.187.118.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 203.28.252.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.17.151.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.22.50.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 161.248.6.0/23 | Valid | RIR databaseAPNIC | 666 99% |
| 157.20.74.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS150180 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 21 are in fix.csv.
- Route object: none2
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.37.185.0/24 | Route objects for it name AS150417. A route object for 103.37.184.0/23 with origin AS150180 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150180 in the RIR database for the space. |
| Route object: none | 202.50.155.0/24 | Route objects for it name AS56264. Add a route object with origin AS150180 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS150180 whose prefix no peer sees AS150180 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.37.184.0/23 | RADB | No ROA |
| 103.163.30.0/23 | RADB | No ROA |
| 103.209.92.0/24 | APNIC | Valid |
| 103.209.93.0/24 | APNIC | Valid |
| 157.20.75.0/24 | APNIC | Valid |
| 160.22.50.0/24 | APNIC | Valid |
| 160.22.51.0/24 | APNIC | Valid |
| 160.30.176.0/24 | APNIC | Valid |
| 160.30.177.0/24 | APNIC | Valid |
| 160.187.118.0/24 | APNIC | Valid |
| 160.187.119.0/24 | APNIC | Valid |
| 161.248.6.0/24 | APNIC | Valid |
| 161.248.7.0/24 | APNIC | Valid |
| 203.28.252.0/24 | APNIC | Valid |
| 203.28.253.0/24 | APNIC | Valid |
| 2001:df0:ddc0::/48 | APNIC, RADB | Valid |
| 2001:df1:3140::/48 | APNIC, RADB | Valid |
| 2001:df1:84c0::/48 | RADB | No ROA |
| 2001:df6:880::/48 | RADB | No 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.