bgpreport

Network · data from 2026-11-12

AS141995 Contabo Asia

Registry name: CAPL-AS-AP - Contabo Asia Private Limited, SG · PeeringDB

89IPv4 routes 95.5% RPKI valid · 97.8% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
3No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS141995, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141995, 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.

46.250.236.15/32 Invalid: maxLength Nonecovered by 46.250.224.0/20 1 0%low visibility 1
154.26.136.0/21 No ROA Other IRR onlyRADB 673 100% 69
154.26.128.0/21 No ROA Other IRR onlyRADB 670 100% 69
154.26.152.0/21 No ROA Other IRR onlyRADB 669 99% 68
5.104.87.147/32 Valid Nonecovered by 5.104.84.0/22 1 0%low visibility 1
94.136.184.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.185.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.186.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.187.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.188.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.189.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.190.0/24 Valid Other IRR onlyRADB 670 100% 66
94.136.191.0/24 Valid Other IRR onlyRADB 670 100% 67
156.67.104.0/24 Valid Other IRR onlyRADB 670 100% 66
156.67.105.0/24 Valid Other IRR onlyRADB 670 100% 66
156.67.110.0/24 Valid Other IRR onlyRADB 670 100% 66
156.67.111.0/24 Valid Other IRR onlyRADB 670 100% 66
13.140.64.0/21 Valid RIR databaseRADB, RIPE 673 100% 69
46.250.224.0/20 Valid RIR databaseRADB, RIPE 673 100% 69
62.72.44.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
62.146.232.0/21 Valid RIR databaseRADB, RIPE 673 100% 69
82.197.68.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
84.247.144.0/21 Valid RIR databaseRADB, RIPE 673 100% 69
103.164.54.0/23 Valid RIR databaseAPNIC, RADB 673 100% 69
109.123.232.0/21 Valid RIR databaseRADB, RIPE 673 100% 69
147.93.156.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
147.93.172.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
147.93.214.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
185.111.159.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
185.227.134.0/23 Valid RIR databaseRADB, RIPE 673 100% 69
185.250.38.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
194.5.153.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
194.195.90.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
194.233.64.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.68.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.72.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.80.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.84.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.88.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
194.233.92.0/22 Valid RIR databaseAPNIC, RADB 673 100% 69
217.216.32.0/21 Valid RIR databaseRADB, RIPE 673 100% 69
217.216.72.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
217.216.108.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
217.217.252.0/22 Valid RIR databaseRADB, RIPE 673 100% 69
62.72.41.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
13.140.72.0/23 Valid RIR databaseRADB, RIPE 671 100% 68
13.140.76.0/23 Valid RIR databaseRADB, RIPE 671 100% 68
13.140.78.0/23 Valid RIR databaseRADB, RIPE 671 100% 68
13.140.248.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
45.80.29.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
46.250.248.0/21 Valid RIR databaseRADB, RIPE 671 100% 68
84.247.152.0/21 Valid RIR databaseRADB, RIPE 671 100% 68
109.123.227.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
109.123.228.0/22 Valid RIR databaseRADB, RIPE 671 100% 68
155.133.7.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
178.212.33.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
194.180.177.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
217.216.76.0/23 Valid RIR databaseRADB, RIPE 671 100% 68
5.104.80.0/22 Valid RIR databaseRADB, RIPE 670 100% 68
5.104.84.0/22 Valid RIR databaseRADB, RIPE 670 100% 68
13.140.56.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
13.140.58.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
13.140.74.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
13.140.252.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
62.72.40.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
62.72.40.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
62.72.42.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
62.72.43.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
82.180.144.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
82.180.144.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
82.180.145.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
82.180.146.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
82.180.147.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
94.136.184.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
94.136.188.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
147.93.152.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
147.93.168.0/22 Valid RIR databaseRADB, RIPE 670 100% 66
156.67.104.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
156.67.110.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
178.212.35.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
185.193.19.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
194.61.31.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
194.233.76.0/22 Valid RIR databaseAPNIC, RADB 670 100% 69
217.15.160.0/21 Valid RIR databaseRADB, RIPE 670 100% 69
217.216.58.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
217.216.78.0/23 Valid RIR databaseRADB, RIPE 670 100% 66
217.217.248.0/22 Valid RIR databaseRADB, RIPE 670 100% 67
80.65.208.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
46.250.240.0/21 Valid RIR databaseRADB, RIPE 668 99% 68
2400:d320::/32 Valid RIR databaseAPNIC, RADB 635 100% 69
2400:d321::/32 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:3641::/32 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:3640::/32 Valid RIR databaseAPNIC, RADB 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS141995: RADB::AS141995:AS-CONE. 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 (AS141995 isn't in the set, or no route object for AS141995 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.

NameDatabaseASNsSets Route objectsAS141995 in itNot covered
RADB::AS141995:AS-CONE RADB 22216 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 27 are in fix.csv.

  • ROA: maxLength1
  • ROA: none3
  • Route object: none2
  • Route object: RIR15
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: maxLength46.250.236.15/32ROA 46.250.224.0/20 AS141995 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 46.250.236.15/32.1 of 673
Route object: none46.250.236.15/32No route object for it. A route object for 46.250.224.0/20 with origin AS141995 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS141995 in the RIR database for the space.1 of 673
ROA: none154.26.136.0/21No ROA covers it. Add a ROA for AS141995, maxLength 21.673 of 673
Route object: RIR154.26.136.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.26.128.0/21No ROA covers it. Add a ROA for AS141995, maxLength 21.670 of 673
Route object: RIR154.26.128.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none154.26.152.0/21No ROA covers it. Add a ROA for AS141995, maxLength 21.669 of 673
Route object: RIR154.26.152.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none5.104.87.147/32No route object for it. A route object for 5.104.84.0/22 with origin AS141995 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS141995 in the RIR database for the space.1 of 673
Route object: RIR94.136.184.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.185.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.186.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.187.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.188.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.189.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.190.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR94.136.191.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR156.67.104.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR156.67.105.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR156.67.110.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR156.67.111.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS141995 whose prefix no peer sees AS141995 announce. Many are kept on purpose (backup routes, space announced only in some places).

46.250.240.0/20RADB, RIPEValid
84.247.144.0/20RIPEValid
154.26.128.0/19RADBNo ROA
154.26.144.0/21RADBNo ROA
204.57.32.0/20NTTCOMValid
2001:470:56a::/48ARINValid

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.