bgpreport

Network · data from 2026-11-12

AS212154 Saru Network

Registry name: SARUNETWORK-AS Wei-Cheng Tsai, TW · PeeringDB

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

Announced routes

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

2a0e:8f02:f047::/48 Invalid: origin None 3 0%low visibility 3
2a05:dfc3:fd0f::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:b107:1c0f::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS212154: AS-SARUNETWORK. 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 (AS212154 isn't in the set, or no route object for AS212154 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 objectsAS212154 in itNot covered
AS-SARUNETWORK RIPE 117 Yes 1

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin2a0e:8f02:f047::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS212154 should announce it, add a ROA for AS212154.3 of 636
Route object: none2a0e:8f02:f047::/48No route object for it. Add a route object with origin AS212154 in the RIR database for the space.3 of 636

Route objects not announced

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

2a05:dfc1:8010::/44RIPEValid
2a05:dfc3:fd00::/48RIPEValid
2a05:dfc3:fd0e::/48RIPEValid
2a0e:b107:1c00::/48RIPENo ROA
2a0e:b107:1c0e::/48RIPENo 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.