Network · data from 2026-11-12
AS141107 Linkgo Metro Teknologi
Registry name: IDNIC-LINKGO-AS-ID - PT Linkgo Metro Teknologi, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141107, 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.66.86.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.157.26.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.157.27.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.169.6.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.169.7.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.187.106.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.210.68.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.210.69.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.216.188.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.220.47.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 124.109.22.0/24 | Valid | Other IRR onlyRADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS141107: AS141107:AS-LINKGO. 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 (AS141107 isn't in the set, or no route object for AS141107 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 | AS141107 in it | Not covered |
|---|---|---|---|---|---|
| AS141107:AS-LINKGO | RADB | 3 | 1 | Yes | 0 |
| APNIC (also) | 3 | 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 16 are in fix.csv.
- Route object: RIR11
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.66.86.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.27.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.169.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.169.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.187.106.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.210.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.210.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.216.188.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.220.47.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 124.109.22.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141107 whose prefix no peer sees AS141107 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.157.26.0/23 | RADB | Valid |
| 103.169.6.0/23 | RADB | Valid |
| 103.210.68.0/23 | RADB | Valid |
| 2001:df1:fe00::/48 | RADB | Valid |
| 2001:df5:b80::/48 | 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.