bgpreport

Network · data from 2026-11-12

AS214339 SRV-RENT SRV.RENT UG (haftungsbeschraenkt)

Registry name: SRV-RENT SRV.RENT UG (haftungsbeschraenkt), DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214339, 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.
2a12:de40:46::/48 No ROA RIR databaseRIPE 634 100% 69
94.156.61.0/24 Valid RIR databaseRIPE 672 100% 66
77.90.56.0/24 Valid RIR databaseRIPE 671 100% 66
2a07:6d40:2::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a12:de40:46::/48No ROA covers it. Add a ROA for AS214339, maxLength 48.634 of 636

Route objects not announced

Every route object with origin AS214339 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.