bgpreport

Network · data from 2026-11-12

AS41480 Systemec

Registry name: SYSTEMEC-AS Systemec BV, NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41480, 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.
212.124.64.0/19 Valid None 673 100% 67
212.124.80.0/20 Valid None 673 100% 67
89.20.64.0/19 Valid RIR databaseRIPE 673 100% 66
89.20.64.0/20 Valid RIR databaseRIPE 673 100% 66
89.20.80.0/20 Valid RIR databaseRIPE 673 100% 66
185.25.164.0/22 Valid RIR databaseRIPE 673 100% 66
185.67.24.0/22 Valid RIR databaseRIPE 673 100% 66
193.25.96.0/24 Valid RIR databaseRIPE 673 100% 66
193.25.97.0/24 Valid RIR databaseRIPE 673 100% 66
212.124.64.0/20 Valid RIR databaseRIPE 673 100% 66
212.124.64.0/22 Valid RIR databaseRIPE 673 100% 66
2a00:8120::/32 Valid RIR databaseRIPE 635 100% 67
2a02:2170::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS41480: AS-SYSTEMEC. 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 (AS41480 isn't in the set, or no route object for AS41480 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 objectsAS41480 in itNot covered
AS-SYSTEMEC RIPE 2116 Yes 2

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none212.124.64.0/19No route object for it. Add a route object with origin AS41480 in the RIR database for the space.673 of 673
Route object: none212.124.80.0/20No route object for it. Add a route object with origin AS41480 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS41480 is announced.

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.