Network · data from 2026-11-12
AS139449 Lintasdata Network
Registry name: LINTASDATA-AS-ID - PT Lintas Data Multimedia, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139449, 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.145.35.0/24 | Valid | None | 673 100% |
| 103.145.34.0/24 | Valid | None | 668 99% |
| 2405:77c0:1000::/36 | Valid | Nonecovered by 2405:77c0::/32 | 636 100% |
| 2405:77c0:1008::/48 | Valid | Nonecovered by 2405:77c0::/32 | 636 100% |
| 2405:77c0:1009::/48 | Valid | Nonecovered by 2405:77c0::/32 | 636 100% |
| 2405:77c0:1000::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1001::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1002::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1003::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1004::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1005::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1006::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:1007::/48 | Valid | Nonecovered by 2405:77c0::/32 | 635 100% |
| 2405:77c0:2::/48 | Valid | Nonecovered by 2405:77c0::/32 | 634 100% |
| 103.179.217.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.179.216.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 2405:77c0::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 103.179.216.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS139449: AS139449:AS-LDM-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 (AS139449 isn't in the set, or no route object for AS139449 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 | AS139449 in it | Not covered |
|---|---|---|---|---|---|
| AS139449:AS-LDM-ID | APNIC | 10 | 1 | 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 14 are in fix.csv.
- Route object: none14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.145.35.0/24 | No route object for it. Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 103.145.34.0/24 | No route object for it. Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1000::/36 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1008::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1009::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1000::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1001::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1002::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1003::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1004::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1005::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1006::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:1007::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
| Route object: none | 2405:77c0:2::/48 | No route object for it. A route object for 2405:77c0::/32 with origin AS139449 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139449 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS139449 is announced.
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.