bgpreport

Network · data from 2026-11-12

AS142005 NC Corporation

Registry name: NCTAIWANCOLTD-AS-AP - NC Taiwan Co., Ltd., TW · PeeringDB

33IPv4 routes 100.0% RPKI valid · 90.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
88Route objects not announced registered with origin AS142005, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS142005, 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.61.3.0/24 Valid Other origin only 4 1%low visibility 4
210.61.107.0/24 Valid None 4 1%low visibility 4
210.242.118.0/24 Valid Other origin only 4 1%low visibility 4
64.25.32.0/23 Valid RIR databaseAPNIC 673 100% 67
64.25.34.0/23 Valid RIR databaseAPNIC 673 100% 67
64.25.36.0/23 Valid RIR databaseAPNIC 673 100% 67
64.25.38.0/23 Valid RIR databaseAPNIC 673 100% 67
64.25.41.0/24 Valid RIR databaseAPNIC 673 100% 67
85.113.86.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
193.149.158.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
193.149.166.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
206.127.144.0/22 Valid RIR databaseAPNIC 673 100% 66
206.127.144.0/23 Valid RIR databaseAPNIC 673 100% 66
206.127.148.0/23 Valid RIR databaseAPNIC 673 100% 66
206.127.152.0/23 Valid RIR databaseAPNIC 673 100% 67
206.127.154.0/23 Valid RIR databaseAPNIC 673 100% 67
206.127.156.0/23 Valid RIR databaseAPNIC 673 100% 67
209.35.96.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
209.35.114.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
209.35.156.0/23 Valid RIR databaseAPNIC, RADB 673 100% 67
209.35.188.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
216.107.240.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
216.107.240.0/24 Valid RIR databaseAPNIC 673 100% 67
216.107.244.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
216.107.248.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
216.107.252.0/22 Valid RIR databaseAPNIC, RADB 673 100% 67
103.164.130.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.164.131.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
206.127.157.0/24 Valid RIR databaseAPNIC 672 100% 67
209.35.97.0/24 Valid RIR databaseAPNIC 672 100% 67
209.35.115.0/24 Valid RIR databaseAPNIC 672 100% 67
64.25.37.0/24 Valid RIR databaseAPNIC 211 31% 55
206.127.156.0/24 Valid RIR databaseAPNIC 46 7%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS142005: RADB::AS-NC-CORPORATION. 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 (AS142005 isn't in the set, or no route object for AS142005 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 objectsAS142005 in itNot covered
RADB::AS-NC-CORPORATION In no IRR database read today.

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 92 are in fix.csv.

  • Route object: none3
  • AS-SET: not found1
  • Route object: not announced88
ChangePrefix or setDetailFull-table peers
Route object: none210.61.3.0/24Route objects for it name AS198949. Add a route object with origin AS142005 in the RIR database for the space.4 of 673
Route object: none210.61.107.0/24No route object for it. Add a route object with origin AS142005 in the RIR database for the space.4 of 673
Route object: none210.242.118.0/24Route objects for it name AS198949. Add a route object with origin AS142005 in the RIR database for the space.4 of 673
AS-SET: not foundRADB::AS-NC-CORPORATIONPeeringDB names RADB::AS-NC-CORPORATION; no IRR database read has it.

Route objects not announced

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

64.25.32.0/20APNIC, RADBValid
64.25.32.0/21APNICValid
64.25.32.0/22APNICValid
64.25.32.0/24APNICValid
64.25.33.0/24APNICValid
64.25.34.0/24APNICValid
64.25.35.0/24APNICValid
64.25.36.0/22APNICValid
64.25.36.0/24APNICValid
64.25.38.0/24APNICValid
64.25.39.0/24APNICValid
64.25.40.0/21APNICValid
64.25.40.0/22APNICValid
64.25.40.0/23APNICValid
64.25.40.0/24APNICValid
64.25.42.0/23APNICValid
64.25.42.0/24APNICValid
64.25.43.0/24APNICValid
64.25.44.0/22APNICValid
64.25.44.0/23APNICValid
64.25.44.0/24APNICValid
64.25.45.0/24APNICValid
64.25.46.0/23APNICValid
64.25.46.0/24APNICValid
64.25.47.0/24APNICValid
85.113.86.0/24APNICValid
85.113.87.0/24APNICValid
103.164.130.0/23APNIC, RADBValid
193.149.158.0/24APNICValid
193.149.159.0/24APNICValid
193.149.166.0/24APNICValid
193.149.167.0/24APNICValid
206.127.144.0/20APNIC, RADBValid
206.127.144.0/21APNICValid
206.127.144.0/24APNICValid
206.127.145.0/24APNICValid
206.127.146.0/23APNICValid
206.127.146.0/24APNICValid
206.127.147.0/24APNICValid
206.127.148.0/22APNICValid
206.127.148.0/24APNICValid
206.127.149.0/24APNICValid
206.127.150.0/23APNICValid
206.127.150.0/24APNICValid
206.127.151.0/24APNICValid
206.127.152.0/21APNICValid
206.127.152.0/22APNICValid
206.127.152.0/24APNICValid
206.127.153.0/24APNICValid
206.127.154.0/24APNICValid
206.127.155.0/24APNICValid
206.127.156.0/22APNICValid
206.127.158.0/23APNICValid
206.127.158.0/24APNICValid
206.127.159.0/24APNICValid
209.35.96.0/24APNICValid
209.35.114.0/24APNICValid
209.35.156.0/24APNICValid
209.35.157.0/24APNICValid
209.35.188.0/24APNICValid
209.35.189.0/24APNICValid
216.107.240.0/20APNIC, RADBValid
216.107.240.0/21APNICValid
216.107.240.0/23APNICValid
216.107.241.0/24APNICValid
216.107.242.0/23APNICValid
216.107.242.0/24APNICValid
216.107.243.0/24APNICValid
216.107.244.0/23APNICValid
216.107.244.0/24APNICValid
216.107.245.0/24APNICValid
216.107.246.0/23APNICValid
216.107.246.0/24APNICValid
216.107.247.0/24APNICValid
216.107.248.0/21APNICValid
216.107.248.0/23APNICValid
216.107.248.0/24APNICValid
216.107.249.0/24APNICValid
216.107.250.0/23APNICValid
216.107.250.0/24APNICValid
216.107.251.0/24APNICValid
216.107.252.0/23APNICValid
216.107.252.0/24APNICValid
216.107.253.0/24APNICValid
216.107.254.0/23APNICValid
216.107.254.0/24APNICValid
216.107.255.0/24APNICValid
2001:df6:4780::/48RADBNo 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.