bgpreport

Network · data from 2026-11-12

AS58329 rackplace

Registry name: SERVINGA-NL servinga GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58329, 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.
79.132.133.0/24 Invalid: origin Other origin only 1 0%low visibility 1
31.214.157.0/24 Valid RIR databaseRIPE 673 100% 67
79.132.128.0/24 Valid RIR databaseRIPE 673 100% 67
79.132.129.0/24 Valid RIR databaseRIPE 673 100% 67
185.158.249.0/24 Valid RIR databaseRIPE 673 100% 67
193.242.210.0/23 Valid RIR databaseRIPE 673 100% 67
194.76.225.0/24 Valid RIR databaseRIPE 673 100% 67
45.155.249.0/24 Valid RIR databaseRIPE 666 99% 67
2001:67c:2ae8::/48 Valid RIR databaseRIPE 634 100% 67
2a0b:7140:6::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS58329: AS-SERVINGA. 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 (AS58329 isn't in the set, or no route object for AS58329 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 objectsAS58329 in itNot covered
AS-SERVINGA RIPE 71100 Yes 1

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin79.132.133.0/24ROAs covering it name AS200220, not AS58329. If AS58329 should announce it, add a ROA for AS58329.1 of 673
Route object: none79.132.133.0/24Route objects for it name AS200220. Add a route object with origin AS58329 in the RIR database for the space.1 of 673

Route objects not announced

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

79.132.132.0/24RIPEValid

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.