bgpreport

Network · data from 2026-11-12

AS18423 RAID

Registry name: RAID-AS-TW - RAID Networks Co., Ltd., TW · PeeringDB

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

Announced routes

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

211.79.104.0/24 No ROA Other origin onlycovered by 211.79.104.0/23 13 2%low visibility 14
211.79.105.0/24 No ROA Nonecovered by 211.79.104.0/23 13 2%low visibility 14
211.79.104.0/23 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS18423: RADB::AS18423:AS-RAID. 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 (AS18423 isn't in the set, or no route object for AS18423 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 objectsAS18423 in itNot covered
RADB::AS18423:AS-RAID RADBlists itself further down15 member sets in no database: AS-ALANYHQ-NETWORKS, AS-LC, AS-NEBURST, AS131657:AS-FASTLINE, AS15143:AS-SET … 4371141,661 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 25 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • AS-SET: missing member15
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none211.79.104.0/24No ROA covers it. Add a ROA for AS18423, maxLength 24.13 of 673
Route object: none211.79.104.0/24Route objects for it name AS21859. A route object for 211.79.104.0/23 with origin AS18423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18423 in the RIR database for the space.13 of 673
ROA: none211.79.105.0/24No ROA covers it. Add a ROA for AS18423, maxLength 24.13 of 673
Route object: none211.79.105.0/24No route object for it. A route object for 211.79.104.0/23 with origin AS18423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18423 in the RIR database for the space.13 of 673
ROA: none211.79.104.0/23No ROA covers it. Add a ROA for AS18423, maxLength 23.672 of 673
Route object: RIR211.79.104.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS-ALANYHQ-NETWORKS; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS-LC; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS-NEBURST; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS131657:AS-FASTLINE; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS15143:AS-SET; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS1659:AS-TANET; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS201705:AS-XLINET; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS202959:AS-LUSHU; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS208223:AS-ALL; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS210352:AS-ZEROWOLF; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS211575:AS-RUINETWORK; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS213430:AS-CLOUDBASE-1; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS213605:AS-PYSIO-NETWORKS-TW; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS38254:AS-ITLAB; no IRR database read has it.
AS-SET: missing memberRADB::AS18423:AS-RAIDAS18423:AS-RAID (RADB) lists AS917:AS-MISAKA; no IRR database read has it.

Route objects not announced

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

61.56.112.0/20NTTCOMNo ROA
103.186.142.0/23RADBNo ROA
103.186.142.0/24RADBNo ROA
103.186.143.0/24RADBNo 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.