Network · data from 2026-11-12
AS138886 Data Buana Nusantara
Registry name: DBN-AS-ID - PT Data Buana Nusantara, ID · PeeringDB
35IPv4 routes
100.0% RPKI valid · 80.0% with a route object
8IPv6 routes
100.0% RPKI valid · 12.5% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS138886, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS138886, 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.28.108.0/22 | Valid | None | 673 100% |
| 103.28.108.0/23 | Valid | None | 673 100% |
| 103.28.108.0/24 | Valid | None | 673 100% |
| 103.28.109.0/24 | Valid | None | 673 100% |
| 103.28.110.0/23 | Valid | None | 673 100% |
| 103.28.110.0/24 | Valid | None | 673 100% |
| 103.28.111.0/24 | Valid | None | 673 100% |
| 2405:1640:1::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:2::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:3::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:4::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:5::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:7::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 2405:1640:8::/48 | Valid | Nonecovered by 2405:1640::/32 | 635 100% |
| 103.13.137.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.73.159.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.141.108.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.141.109.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.163.36.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.163.37.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.189.120.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.189.121.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.189.122.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 117.18.20.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 117.18.20.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 117.18.21.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 117.18.22.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 117.18.23.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.154.44.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.154.45.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.141.108.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 210.87.118.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 210.87.118.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 210.87.119.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2405:1640::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 202.58.72.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.73.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.74.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.75.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.76.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.77.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.78.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.58.79.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS138886: AS-DBN. 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 (AS138886 isn't in the set, or no route object for AS138886 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 | AS138886 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-DBN | 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 45 are in fix.csv.
- Route object: none14
- Route object: RIR21
- AS-SET: not found1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.28.108.0/22 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.108.0/23 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.108.0/24 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.109.0/24 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.110.0/23 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.110.0/24 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 103.28.111.0/24 | No route object for it. Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:1::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:2::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:3::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:4::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:5::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:7::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: none | 2405:1640:8::/48 | No route object for it. A route object for 2405:1640::/32 with origin AS138886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS138886 in the RIR database for the space. |
| Route object: RIR | 103.13.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.73.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.141.108.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.141.109.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.163.36.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.163.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.189.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.189.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.189.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.20.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.20.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.21.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.22.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 117.18.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.154.44.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.154.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.141.108.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.87.118.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.87.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.87.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2405:1640::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS-DBN | PeeringDB names AS-DBN; no IRR database read has it. |
Route objects not announced
Route objects with origin AS138886 whose prefix no peer sees AS138886 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.163.36.0/23 | RADB | Valid |
| 103.189.120.0/23 | RADB | Valid |
| 202.58.72.0/21 | APNIC | Valid |
| 202.58.72.0/22 | APNIC | Valid |
| 202.58.72.0/23 | APNIC | Valid |
| 202.58.74.0/23 | APNIC | Valid |
| 202.58.76.0/22 | APNIC | Valid |
| 202.58.76.0/23 | APNIC | Valid |
| 202.58.78.0/23 | 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.