Network · data from 2026-11-12
AS136106 FiberStar AS136106
Registry name: FIBERSTAR-AS-ID - PT. Mega Akses Persada, ID · PeeringDB
19IPv4 routes
89.5% RPKI valid · 42.1% with a route object
8IPv6 routes
100.0% RPKI valid · 12.5% with a route object
2RPKI invalid
2 origin · 0 maxLength
0No ROA
18 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS136106, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS136106, 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.52.59.101/32 | Invalid: origin | None | 2 0%low visibility |
| 202.52.59.103/32 | Invalid: origin | None | 2 0%low visibility |
| 103.87.184.0/24 | Valid | Nonecovered by 103.87.184.0/23 | 673 100% |
| 103.87.185.0/24 | Valid | Nonecovered by 103.87.184.0/23 | 673 100% |
| 103.87.187.0/24 | Valid | Nonecovered by 103.87.186.0/23 | 673 100% |
| 123.176.122.0/24 | Valid | Nonecovered by 123.176.122.0/23 | 673 100% |
| 123.176.123.0/24 | Valid | Nonecovered by 123.176.122.0/23 | 673 100% |
| 123.176.124.0/24 | Valid | Nonecovered by 123.176.124.0/22 | 673 100% |
| 123.176.125.0/24 | Valid | Nonecovered by 123.176.124.0/22 | 673 100% |
| 123.176.126.0/23 | Valid | Nonecovered by 123.176.124.0/22 | 673 100% |
| 123.176.127.0/24 | Valid | Nonecovered by 123.176.124.0/22 | 673 100% |
| 2400:d740::/33 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740::/34 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740::/48 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740:4000::/34 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740:8000::/33 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740:8000::/34 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 2400:d740:c000::/34 | Valid | Nonecovered by 2400:d740::/32 | 636 100% |
| 103.87.184.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.87.186.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.206.186.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 123.176.121.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 123.176.122.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 123.176.124.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 123.176.126.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.87.184.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 2400:d740::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS136106: AS-FIBERSTAR. 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 (AS136106 isn't in the set, or no route object for AS136106 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 | AS136106 in it | Not covered |
|---|---|---|---|---|---|
| AS-FIBERSTAR | RADB2 member sets in no database: AS-CBN-ID, AS-MEDIALINK | 1,302 | 569 | Yes | 2 |
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 37 are in fix.csv.
- ROA: origin2
- Route object: none18
- Route object: RIR7
- AS-SET: missing member2
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 202.52.59.101/32 | ROAs covering it name AS46058, not AS136106. If AS136106 should announce it, add a ROA for AS136106. |
| Route object: none | 202.52.59.101/32 | No route object for it. Add a route object with origin AS136106 in the RIR database for the space. |
| ROA: origin | 202.52.59.103/32 | ROAs covering it name AS46058, not AS136106. If AS136106 should announce it, add a ROA for AS136106. |
| Route object: none | 202.52.59.103/32 | No route object for it. Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 103.87.184.0/24 | No route object for it. A route object for 103.87.184.0/23 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 103.87.185.0/24 | No route object for it. A route object for 103.87.184.0/23 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 103.87.187.0/24 | No route object for it. A route object for 103.87.186.0/23 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.122.0/24 | No route object for it. A route object for 123.176.122.0/23 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.123.0/24 | No route object for it. A route object for 123.176.122.0/23 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.124.0/24 | No route object for it. A route object for 123.176.124.0/22 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.125.0/24 | No route object for it. A route object for 123.176.124.0/22 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.126.0/23 | No route object for it. A route object for 123.176.124.0/22 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 123.176.127.0/24 | No route object for it. A route object for 123.176.124.0/22 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740::/33 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740::/34 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740::/48 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740:4000::/34 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740:8000::/33 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740:8000::/34 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: none | 2400:d740:c000::/34 | No route object for it. A route object for 2400:d740::/32 with origin AS136106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136106 in the RIR database for the space. |
| Route object: RIR | 103.87.184.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.87.186.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.206.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.176.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.176.122.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.176.124.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 123.176.126.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-FIBERSTAR | AS-FIBERSTAR (RADB) lists AS-CBN-ID; no IRR database read has it. |
| AS-SET: missing member | AS-FIBERSTAR | AS-FIBERSTAR (RADB) lists AS-MEDIALINK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS136106 whose prefix no peer sees AS136106 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.164.132.0/24 | APNIC | Invalid: origin |
| 103.164.133.0/24 | APNIC | Invalid: origin |
| 103.164.134.0/24 | APNIC | Invalid: origin |
| 103.164.135.0/24 | APNIC | Invalid: origin |
| 123.253.128.0/24 | APNIC | Invalid: origin |
| 123.253.129.0/24 | APNIC | Invalid: origin |
| 123.253.130.0/24 | APNIC | Invalid: origin |
| 123.253.131.0/24 | APNIC | Invalid: origin |
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.