Network · data from 2026-11-12
AS137526 Plusnet Inc
Registry name: PLUSNETINC-AS-AP - Plusnet Inc, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137526, 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.20.243.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 103.111.224.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.111.225.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.111.226.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.111.227.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.153.170.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.153.171.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.186.238.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 45.125.30.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 45.125.31.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.186.239.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.250.241.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 202.1.29.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 2402:a1c0::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:a1c0::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:a1c0:1000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2402:a1c0:f000::/48 | Valid | RIR databaseAPNIC | 48 8%low visibility |
| 103.156.181.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS137526: AS-PLUSNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS137526 isn't in the set, or no route object for AS137526 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS137526 in it | Not covered |
|---|---|---|---|---|---|
| AS-PLUSNET | RIPE | 65 | 2 | No | 18 |
| APNIC (also) | 31 | 1 | No | 18 |
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 9 are in fix.csv.
- ROA: origin1
- Route object: none1
- AS-SET: own ASN1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.20.243.0/24 | ROAs covering it name AS135075, not AS137526. If AS137526 should announce it, add a ROA for AS137526. |
| Route object: none | 103.20.243.0/24 | Route objects for it name AS135075. Add a route object with origin AS137526 in the RIR database for the space. |
| AS-SET: own ASN | AS-PLUSNET | AS137526 isn't in AS-PLUSNET (RIPE) once expanded. Add AS137526 to it. |
Route objects not announced
Route objects with origin AS137526 whose prefix no peer sees AS137526 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.67.63.0/24 | APNIC | Valid |
| 103.111.224.0/22 | APNIC | Valid |
| 103.153.170.0/23 | APNIC | Valid |
| 103.186.238.0/23 | APNIC | Valid |
| 2400:75e0::/32 | APNIC | Valid |
| 2402:7ca0::/32 | 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.