bgpreport

Network · data from 2026-11-12

AS211895 Serverius-Users-as Serverius Holding B.V.

Registry name: Serverius-Users-as Serverius Holding B.V., NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211895, 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.
191.44.121.0/24 Invalid: origin None 87 13% 39
88.218.30.0/24 No ROA RIR databaseRIPE 672 100% 67
94.247.214.0/24 No ROA RIR databaseRIPE 672 100% 67
91.208.52.0/24 No ROA RIR databaseRIPE 671 100% 67
45.155.7.0/24 No ROA RIR databaseRIPE 670 100% 67
2a09:4d41::/32 No ROA RIR databaseRIPE 632 99% 67
2a14:2000::/29 No ROA RIR databaseRIPE 628 99% 67
31.43.163.0/24 Valid RIR databaseRIPE 672 100% 67
82.41.2.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
85.204.127.0/24 Valid RIR databaseRIPE 672 100% 67
89.33.163.0/24 Valid RIR databaseRIPE 672 100% 67
91.198.77.0/24 Valid RIR databaseRIPE 672 100% 67
103.42.240.0/24 Valid RIR databaseAPNIC 672 100% 67
193.111.32.0/24 Valid RIR databaseRIPE 672 100% 67
2001:67c:21b4::/48 Valid RIR databaseRIPE 634 100% 67
2a0f:8cc0::/48 Valid RIR databaseRIPE 634 100% 67
2a11:b100:c100::/48 Valid RIR databaseRIPE 632 99% 67
2a14:bc80:102::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS211895 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin191.44.121.0/24ROAs covering it name AS34346, not AS211895. If AS211895 should announce it, add a ROA for AS211895.87 of 673
Route object: none191.44.121.0/24No route object for it. Add a route object with origin AS211895 in the RIR database for the space.87 of 673
ROA: none88.218.30.0/24No ROA covers it. Add a ROA for AS211895, maxLength 24.672 of 673
ROA: none94.247.214.0/24No ROA covers it. Add a ROA for AS211895, maxLength 24.672 of 673
ROA: none91.208.52.0/24No ROA covers it. Add a ROA for AS211895, maxLength 24.671 of 673
ROA: none45.155.7.0/24No ROA covers it. Add a ROA for AS211895, maxLength 24.670 of 673
ROA: none2a09:4d41::/32No ROA covers it. Add a ROA for AS211895, maxLength 32.632 of 636
ROA: none2a14:2000::/29No ROA covers it. Add a ROA for AS211895, maxLength 29.628 of 636

Route objects not announced

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

2a13:36c0::/32RIPENo 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.