bgpreport

Network · data from 2026-11-12

AS212094 AndreSchmidt

Registry name: Schmidt-IT-Solutions Andre Schmidt, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212094, 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:97c0:489::/48 Valid Nonecovered by 2a0e:97c0:488::/45 633 100% 69
2a0e:97c0:48a::/48 Valid Nonecovered by 2a0e:97c0:488::/45 633 100% 69
2a0e:97c0:488::/48 Valid Nonecovered by 2a0e:97c0:488::/45 1 0%low visibility 1
2a0e:97c0:486::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2a0e:97c0:487::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS212094's PeeringDB record names no AS-SET.

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

  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2a0e:97c0:489::/48No route object for it. A route object for 2a0e:97c0:488::/45 with origin AS212094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212094 in the RIR database for the space.633 of 636
Route object: none2a0e:97c0:48a::/48No route object for it. A route object for 2a0e:97c0:488::/45 with origin AS212094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212094 in the RIR database for the space.633 of 636
Route object: none2a0e:97c0:488::/48No route object for it. A route object for 2a0e:97c0:488::/45 with origin AS212094 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212094 in the RIR database for the space.1 of 636

Route objects not announced

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

2a06:de01:e0::/44RIPEValid
2a0e:97c0:480::/48RIPEValid
2a0e:97c0:481::/48RIPEValid
2a0e:97c0:482::/48RIPEValid
2a0e:97c0:483::/48RIPEValid
2a0e:97c0:484::/48RIPEValid
2a0e:97c0:485::/48RIPEValid
2a0e:97c0:488::/45RIPEValid

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.