Network · data from 2026-11-12
AS45305 Lintas Data Prima
Registry name: LDP-AS-ID - Lintas Data Prima, PT, ID · PeeringDB
53IPv4 routes
98.1% RPKI valid · 73.6% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
0No ROA
14 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
45Route objects not announced
registered with origin AS45305, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS45305, 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.
| 210.57.214.88/32 | Invalid: origin | None | 2 0%low visibility |
| 103.114.52.0/24 | Valid | Other origin only | 673 100% |
| 103.134.223.0/24 | Valid | Other origin only | 673 100% |
| 103.189.97.0/24 | Valid | Nonecovered by 103.189.96.0/23 | 673 100% |
| 103.190.115.0/24 | Valid | Nonecovered by 103.190.114.0/23 | 673 100% |
| 103.251.153.0/24 | Valid | None | 673 100% |
| 103.83.98.0/24 | Valid | Other origin only | 672 100% |
| 103.100.180.0/23 | Valid | None | 672 100% |
| 103.100.181.0/24 | Valid | Other origin only | 672 100% |
| 103.190.114.0/24 | Valid | Nonecovered by 103.190.114.0/23 | 672 100% |
| 103.175.241.0/24 | Valid | Nonecovered by 103.175.240.0/23 | 670 100% |
| 103.189.96.0/24 | Valid | Nonecovered by 103.189.96.0/23 | 670 100% |
| 103.175.240.0/24 | Valid | Nonecovered by 103.175.240.0/23 | 668 99% |
| 103.220.22.0/24 | Valid | Other origin only | 1 0%low visibility |
| 43.252.105.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.106.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 43.252.107.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.22.99.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.46.10.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.46.11.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.51.205.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.54.80.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.54.81.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.87.149.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.98.122.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.100.182.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.184.181.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 160.19.145.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 160.22.65.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.100.180.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.130.116.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.184.180.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 160.22.64.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.51.204.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.87.148.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 103.130.117.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 2001:df0:a3::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2001:df1:6380::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 103.28.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.28.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.28.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.183.94.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 124.40.250.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 124.40.252.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 124.40.254.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 124.40.255.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.56.164.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.47.188.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.47.189.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.56.165.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.56.167.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 124.40.249.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.28.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 124.40.251.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 202.56.166.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
AS-SET
PeeringDB's irr_as_set for AS45305: AS45305:AS-LDP. 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 (AS45305 isn't in the set, or no route object for AS45305 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 | AS45305 in it | Not covered |
|---|---|---|---|---|---|
| AS45305:AS-LDP | APNIC | 25 | 1 | Yes | 8 |
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 84 are in fix.csv.
- ROA: origin1
- Route object: none14
- Route object: RIR24
- Route object: not announced45
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 210.57.214.88/32 | ROAs covering it name AS38142, not AS45305. If AS45305 should announce it, add a ROA for AS45305. |
| Route object: none | 210.57.214.88/32 | No route object for it. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.114.52.0/24 | Route objects for it name AS137349. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.134.223.0/24 | Route objects for it name AS138810. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.189.97.0/24 | No route object for it. A route object for 103.189.96.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.190.115.0/24 | No route object for it. A route object for 103.190.114.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.251.153.0/24 | No route object for it. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.83.98.0/24 | Route objects for it name AS136078. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.100.180.0/23 | No route object for it. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.100.181.0/24 | Route objects for it name AS136840. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.190.114.0/24 | No route object for it. A route object for 103.190.114.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.175.241.0/24 | No route object for it. A route object for 103.175.240.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.189.96.0/24 | No route object for it. A route object for 103.189.96.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.175.240.0/24 | No route object for it. A route object for 103.175.240.0/23 with origin AS45305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: none | 103.220.22.0/24 | Route objects for it name AS141607. Add a route object with origin AS45305 in the RIR database for the space. |
| Route object: RIR | 43.252.105.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 43.252.107.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.22.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.46.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.46.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.51.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.54.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.54.81.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.87.149.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.98.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.100.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.19.145.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.22.65.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.100.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.130.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.22.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.51.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.87.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.130.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df0:a3::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df1:6380::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45305 whose prefix no peer sees AS45305 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.252.104.0/22 | APNIC, NTTCOM, RADB | Valid |
| 43.252.104.0/23 | NTTCOM, RADB | Valid |
| 43.252.104.0/24 | NTTCOM, RADB | Valid |
| 43.252.106.0/23 | NTTCOM, RADB | Valid |
| 103.28.112.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.28.112.0/23 | NTTCOM, RADB | Valid |
| 103.28.114.0/23 | NTTCOM, RADB | Valid |
| 103.46.10.0/23 | RADB | Valid |
| 103.51.204.0/23 | RADB | Valid |
| 103.54.80.0/23 | RADB | Valid |
| 103.87.148.0/23 | RADB | Valid |
| 103.130.116.0/23 | RADB | No ROA |
| 103.142.254.0/23 | RADB | Valid |
| 103.142.254.0/24 | RADB | Valid |
| 103.142.255.0/24 | RADB | Valid |
| 103.175.240.0/23 | RADB | Valid |
| 103.183.254.0/24 | RADB | Valid |
| 103.189.96.0/23 | RADB | Valid |
| 103.190.114.0/23 | RADB | Valid |
| 103.191.94.0/24 | APNIC | Valid |
| 103.208.100.0/22 | RADB | No ROA |
| 103.237.32.0/24 | NTTCOM, RADB | No ROA |
| 103.237.33.0/24 | NTTCOM, RADB | No ROA |
| 103.237.34.0/24 | NTTCOM, RADB | No ROA |
| 103.237.35.0/24 | NTTCOM, RADB | No ROA |
| 103.254.104.0/24 | REACH | Invalid: origin |
| 103.254.106.0/24 | REACH | Invalid: origin |
| 124.40.248.0/21 | APNIC, NTTCOM, RADB | Valid |
| 124.40.248.0/22 | NTTCOM, RADB | Valid |
| 124.40.248.0/23 | NTTCOM, RADB | Valid |
| 124.40.248.0/24 | APNIC, NTTCOM, RADB | Valid |
| 124.40.250.0/23 | NTTCOM, RADB | Valid |
| 124.40.252.0/22 | NTTCOM, RADB | Valid |
| 124.40.252.0/23 | NTTCOM, RADB | Valid |
| 124.40.253.0/24 | APNIC, NTTCOM, RADB | Valid |
| 124.40.254.0/23 | NTTCOM, RADB | Valid |
| 160.22.64.0/23 | RADB | Valid |
| 202.47.188.0/23 | APNIC | Valid |
| 202.56.164.0/22 | RADB | Valid |
| 202.56.164.0/23 | RADB | Valid |
| 202.56.166.0/23 | RADB | Valid |
| 1:df2:ed40::/48 | RADB | No ROA |
| 2001:df2:f00::/48 | RADB | No ROA |
| 2001:df3:d440::/48 | RADB | No ROA |
| 2001:df7:8b00::/48 | 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.