bgpreport

Network · data from 2026-11-12

AS34568 ConnectingBytes GmbH

Registry name: CONNECTINGBYTES-AS ConnectingBytes GmbH, DE · PeeringDB

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

Announced routes

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

45.15.100.0/24 No ROA RIR databaseRIPE 672 100% 66
45.15.102.0/24 No ROA RIR databaseRIPE 672 100% 66
45.15.103.0/24 No ROA RIR databaseRIPE 672 100% 66
2a0e:2980::/48 No ROA RIR databaseRIPE 635 100% 67
2a0e:2980:2::/48 No ROA RIR databaseRIPE 635 100% 67
84.246.120.0/21 Valid RIR databaseRIPE 673 100% 66
109.234.223.0/24 Valid RIR databaseRIPE 673 100% 66
2a01:1f8::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS34568: AS-CONNECTINGBYTES. 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 (AS34568 isn't in the set, or no route object for AS34568 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 objectsAS34568 in itNot covered
AS-CONNECTINGBYTES RIPE 3123 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 10 are in fix.csv.

  • ROA: none5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none45.15.100.0/24No ROA covers it. Add a ROA for AS34568, maxLength 24.672 of 673
ROA: none45.15.102.0/24No ROA covers it. Add a ROA for AS34568, maxLength 24.672 of 673
ROA: none45.15.103.0/24No ROA covers it. Add a ROA for AS34568, maxLength 24.672 of 673
ROA: none2a0e:2980::/48No ROA covers it. Add a ROA for AS34568, maxLength 48.635 of 636
ROA: none2a0e:2980:2::/48No ROA covers it. Add a ROA for AS34568, maxLength 48.635 of 636

Route objects not announced

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

77.87.248.0/21RIPEValid
84.246.125.0/24RIPEValid
84.246.127.0/24RIPEValid
193.138.81.0/24RIPEValid
194.116.234.0/23RIPENo 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.