Network · data from 2026-11-12
AS137703 Noakhali Broadband Network
Registry name: NBN-AS-AP - Noakhali Broadband Network, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137703, 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.113.192.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.113.194.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.113.195.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.113.193.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2404:5e40::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:5e40:1::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:2::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:3::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:4::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:5::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:7::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:17::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:113::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:195::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:8000::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:8001::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:8004::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:5e40:9::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:5e40:3e8::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:5e40:8::/48 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 2404:5e40:8003::/48 | Valid | RIR databaseAPNIC | 1 0%low visibility |
| 2404:5e40::/32 | Valid | RIR databaseAPNIC | 0 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS137703: AS137703:AS-AP. 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 (AS137703 isn't in the set, or no route object for AS137703 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 | AS137703 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS137703:AS-AP | In no IRR database read today. | |||||
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 13 are in fix.csv.
- AS-SET: not found1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS137703:AS-AP | PeeringDB names AS137703:AS-AP; no IRR database read has it. |
Route objects not announced
Route objects with origin AS137703 whose prefix no peer sees AS137703 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2404:5e40::/33 | APNIC | Valid |
| 2404:5e40:6::/48 | APNIC | Valid |
| 2404:5e40:a::/48 | APNIC | Valid |
| 2404:5e40:b::/48 | APNIC | Valid |
| 2404:5e40:c::/48 | APNIC | Valid |
| 2404:5e40:d::/48 | APNIC | Valid |
| 2404:5e40:e::/48 | APNIC | Valid |
| 2404:5e40:f::/48 | APNIC | Valid |
| 2404:5e40:28::/48 | APNIC | Valid |
| 2404:5e40:8000::/33 | APNIC | Valid |
| 2404:5e40:8002::/48 | APNIC | Valid |
| 2404:5e40:8005::/48 | 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.