bgpreport

Network · data from 2026-11-12

AS50989 DCS Networks

Registry name: DCS-Networks-AS SITAB Infrastruktur, SE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50989, 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.

193.234.32.0/21 No ROA RIR databaseRIPE 1 0%low visibility 1
193.104.214.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS50989: AS-I2B. 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 (AS50989 isn't in the set, or no route object for AS50989 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 objectsAS50989 in itNot covered
AS-I2B RIPE1 member set in no database: AS199746:AS-NEXTSERV 230678,968 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 5 are in fix.csv.

  • ROA: none1
  • AS-SET: missing member1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none193.234.32.0/21No ROA covers it. Add a ROA for AS50989, maxLength 21.1 of 673
AS-SET: missing memberAS-I2BAS-I2B (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

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

193.234.15.0/24RIPENo ROA
195.189.182.0/23RIPENo ROA
2a00:1c20::/32RIPEValid

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.