Network · data from 2026-11-12
AS137823 Technocore Bangladesh
Registry name: TECHNOCORE-AS-AP - cloudone, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137823, 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.
| 165.99.39.0/24 | Invalid: origin | Other origin only | 131 19% |
| 103.115.24.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.115.24.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.115.25.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.115.26.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.115.27.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS137823: AS-SET137823. 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 (AS137823 isn't in the set, or no route object for AS137823 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 | AS137823 in it | Not covered |
|---|---|---|---|---|---|
| AS-SET137823 | APNIC | 0 | 1 | No | 6 |
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 8 are in fix.csv.
- ROA: origin1
- Route object: none1
- AS-SET: own ASN1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 165.99.39.0/24 | ROAs covering it name AS140919, not AS137823. If AS137823 should announce it, add a ROA for AS137823. |
| Route object: none | 165.99.39.0/24 | Route objects for it name AS140919. Add a route object with origin AS137823 in the RIR database for the space. |
| AS-SET: own ASN | AS-SET137823 | AS137823 isn't in AS-SET137823 (APNIC) once expanded. Add AS137823 to it. |
Route objects not announced
Route objects with origin AS137823 whose prefix no peer sees AS137823 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.115.24.0/23 | APNIC | Valid |
| 103.115.26.0/23 | APNIC | Valid |
| 2402:dbc0::/32 | APNIC | Valid |
| 2402:dbc0:4000::/34 | APNIC | Valid |
| 2402:dbc0:4000::/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.