bgpreport

Network · data from 2026-11-12

AS18043 Department of Education, Hsinchu City

Registry name: HCCG-AS - Department of Education, Hsinchu City, TW · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18043, 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.
2001:288:4200::/39 Valid None 632 99% 69
120.104.0.0/19 Valid None 100 15% 37
120.104.32.0/21 Valid None 100 15% 37
120.104.64.0/19 Valid None 100 15% 37
120.104.96.0/20 Valid None 100 15% 37
163.19.104.0/21 Valid None 100 15% 37
163.19.112.0/20 Valid None 100 15% 37
163.19.128.0/20 Valid None 100 15% 37
163.19.144.0/21 Valid None 100 15% 37
163.28.69.0/24 Valid None 98 15% 37
2402:3ce0::/32 Valid RIR databaseAPNIC 632 99% 69
144.79.66.0/23 Valid RIR databaseAPNIC 98 15% 37

AS-SET

PeeringDB's irr_as_set for AS18043: APNIC::AS18043:AS-HGGC. 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 (AS18043 isn't in the set, or no route object for AS18043 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 objectsAS18043 in itNot covered
APNIC::AS18043:AS-HGGC APNIC 114 Yes 10

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

  • Route object: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2001:288:4200::/39No route object for it. Add a route object with origin AS18043 in the RIR database for the space.632 of 636
Route object: none120.104.0.0/19No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none120.104.32.0/21No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none120.104.64.0/19No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none120.104.96.0/20No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none163.19.104.0/21No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none163.19.112.0/20No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none163.19.128.0/20No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none163.19.144.0/21No route object for it. Add a route object with origin AS18043 in the RIR database for the space.100 of 673
Route object: none163.28.69.0/24No route object for it. Add a route object with origin AS18043 in the RIR database for the space.98 of 673

Route objects not announced

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

144.79.66.0/24APNICValid
144.79.67.0/24APNICValid

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.