Network · data from 2026-11-12
AS141071 Jembatan Data Pangrango
Registry name: JEMBATANDATA-AS-ID - PT Jembatan Data Pangrango, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141071, 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.
| 202.57.21.0/24 | Valid | Other origin onlycovered by 202.57.20.0/23 | 673 100% |
| 103.54.171.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.97.140.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.97.141.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.155.196.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 2406:7640::/32 | Valid | Other IRR onlyRADB | 349 55% |
| 202.57.19.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.57.20.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.57.20.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS141071: RADB::AS141071:AS-JDP. 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 (AS141071 isn't in the set, or no route object for AS141071 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 | AS141071 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS141071:AS-JDP | RADB | 25 | 1 | Yes | 0 |
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.
- Route object: none1
- Route object: RIR5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 202.57.21.0/24 | Route objects for it name AS9989. A route object for 202.57.20.0/23 with origin AS141071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS141071 in the RIR database for the space. |
| Route object: RIR | 103.54.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.97.140.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.97.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.155.196.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2406:7640::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141071 whose prefix no peer sees AS141071 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.155.196.0/24 | RADB | Valid |
| 103.155.197.0/24 | RADB | 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.