bgpreport

Network · data from 2026-11-12

AS131657 Fast Line

Registry name: AS-FASTLINE - Hong Da Storage Equipment Co., Ltd., TW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131657, 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.153.176.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
103.122.189.0/24 Valid RIR databaseAPNIC 668 99% 67
138.252.10.0/23 Valid RIR databaseAPNIC, RADB 667 99% 67
163.61.124.0/23 Valid RIR databaseAPNIC, RADB 667 99% 67
210.1.234.0/23 Valid RIR databaseAPNIC, RADB 666 99% 67
138.252.10.0/24 Valid RIR databaseAPNIC 654 97% 70
144.48.34.0/24 Valid RIR databaseAPNIC 654 97% 70
163.61.124.0/24 Valid RIR databaseAPNIC, RADB 654 97% 70
210.1.234.0/24 Valid RIR databaseAPNIC 654 97% 70
103.122.188.0/24 Valid RIR databaseAPNIC 653 97% 67
103.122.190.0/24 Valid RIR databaseAPNIC, RADB 653 97% 67
103.122.191.0/24 Valid RIR databaseAPNIC, RADB 653 97% 67
138.252.54.0/24 Valid RIR databaseAPNIC 653 97% 67
223.26.2.0/23 Valid RIR databaseAPNIC 653 97% 70
2406:48c0:1176::/48 Valid RIR databaseAPNIC 636 100% 70
2406:48c0:1177::/48 Valid RIR databaseAPNIC 636 100% 70
2406:48c0:1189::/48 Valid RIR databaseAPNIC 636 100% 70
103.153.176.0/24 Valid RIR databaseAPNIC, RADB 119 18% 43
103.153.177.0/24 Valid RIR databaseAPNIC, RADB 98 15% 37
138.252.11.0/24 Valid RIR databaseAPNIC 98 15% 37
163.61.125.0/24 Valid RIR databaseAPNIC, RADB 98 15% 37
210.1.235.0/24 Valid RIR databaseAPNIC 98 15% 37

AS-SET

PeeringDB's irr_as_set for AS131657: APNIC::AS131657:AS-FASTLINE. 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 (AS131657 isn't in the set, or no route object for AS131657 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 objectsAS131657 in itNot covered
APNIC::AS131657:AS-FASTLINE APNIC1 member set in no database: AS-LAZCO 3341,563 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 28 are in fix.csv.

  • AS-SET: missing member1
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAPNIC::AS131657:AS-FASTLINEAS131657:AS-FASTLINE (APNIC) lists AS-LAZCO; no IRR database read has it.

Route objects not announced

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

103.23.110.0/23APNICValid
103.23.110.0/24APNICValid
103.23.111.0/24APNICValid
103.51.88.0/23APNIC, RADBValid
103.51.88.0/24APNIC, RADBValid
103.51.89.0/24APNIC, RADBValid
103.51.90.0/23APNIC, RADBValid
103.51.90.0/24APNIC, RADBValid
103.51.91.0/24APNIC, RADBValid
103.122.188.0/22APNICValid
103.196.172.0/23APNICValid
103.196.172.0/24APNICValid
103.196.173.0/24APNICValid
138.252.54.0/23RADBValid
138.252.55.0/24APNICValid
202.5.10.0/23APNICValid
202.5.10.0/24APNICValid
202.5.11.0/24APNICValid
223.26.2.0/24APNICValid
223.26.3.0/24APNICValid
2400:c9a0::/32RADBValid
2400:c9e0::/32RADBValid
2406:48c0::/32APNICValid
2406:48c0:1188::/48APNICValid
2406:48c0:1190::/48APNICValid
2406:48c0:1191::/48APNICValid
2406:48c0:1223::/48APNICValid

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.