Network · data from 2026-11-12
AS136856 Tower Bersama
Registry name: IDNIC-BERSAMANET-AS-ID - PT. Tower Bersama, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136856, 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.102.113.0/24 | Invalid: origin | Nonecovered by 103.102.112.0/23 | 3 0%low visibility |
| 103.102.112.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 103.102.112.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.102.114.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.102.115.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS136856: AS136856:AS-BERSAMANET-ID. 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 (AS136856 isn't in the set, or no route object for AS136856 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 | AS136856 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS136856:AS-BERSAMANET-ID | 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 9 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR4
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.102.113.0/24 | ROAs covering it name AS135610, not AS136856. If AS136856 should announce it, add a ROA for AS136856. |
| Route object: none | 103.102.113.0/24 | No route object for it. A route object for 103.102.112.0/23 with origin AS136856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136856 in the RIR database for the space. |
| ROA: none | 103.102.112.0/23 | No ROA covers it. Add a ROA for AS136856, maxLength 23. |
| Route object: RIR | 103.102.112.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.112.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.114.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.115.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS136856:AS-BERSAMANET-ID | PeeringDB names AS136856:AS-BERSAMANET-ID; no IRR database read has it. |
Route objects not announced
Route objects with origin AS136856 whose prefix no peer sees AS136856 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.102.112.0/22 | RADB | No ROA |
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.