bgpreport

Network · data from 2026-11-12

AS218832 NextServ - DE

Registry name: SHRDSERV NextServ UG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS218832, 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.
2a05:dfc6:2000::/36 Invalid: origin Other IRR onlyALTDB 1 0%low visibility 1
2a14:7581:5101::/48 Valid RIR databaseALTDB, RIPE 633 100% 69
2a14:7581:5030::/44 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS218832: AFRINIC::AS-NOC. 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 (AS218832 isn't in the set, or no route object for AS218832 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 objectsAS218832 in itNot covered
AFRINIC::AS-NOC AFRINIC1 member set in no database: AS-NETUTILS 7162 Yes 0

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: RIR1
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: origin2a05:dfc6:2000::/36ROAs covering it name AS133752, not AS218832. If AS218832 should announce it, add a ROA for AS218832.1 of 636
Route object: RIR2a05:dfc6:2000::/36Route object only in ALTDB. Add it in the RIR database for the space.1 of 636
AS-SET: missing memberAFRINIC::AS-NOCAS-NOC (AFRINIC) lists AS-NETUTILS; no IRR database read has it.

Route objects not announced

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