Network · data from 2026-11-12

AS9136 WOBCOM

Registry name: WOBCOM Wobcom GmbH, DE · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object

10IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS9136, seen from no peer

Announced routes

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


5.159.24.0/21	Valid	RIR databaseRIPE	673 100%	66
62.176.224.0/19	Valid	RIR databaseRIPE	673 100%	66
91.186.32.0/19	Valid	RIR databaseRIPE	673 100%	66
92.118.192.0/22	Valid	RIR databaseRIPE	673 100%	66
185.72.232.0/22	Valid	RIR databaseRIPE	673 100%	66
213.162.128.0/19	Valid	RIR databaseRIPE	673 100%	66
143.163.64.0/23	Valid	RIR databaseRIPE	672 100%	66
185.225.135.0/24	Valid	RIR databaseRIPE	672 100%	66
194.39.104.0/22	Valid	RIR databaseRIPE	672 100%	66
2a01:581:6::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:7::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:8::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:9::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:a::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:b::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:c::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:581:d::/48	Valid	RIR databaseRIPE	635 100%	67
2a01:580::/29	Valid	RIR databaseRIPE	634 100%	67
2a0d:c405::/32	Valid	RIR databaseRIPE	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS9136: RIPE::AS-WOBCOM. 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 (AS9136 isn't in the set, or no route object for AS9136 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.

Name	Database	ASNs	Sets	Route objects	AS9136 in it	Not covered
RIPE::AS-WOBCOM	RIPElists itself further down2 member sets in no database: AS-PBB, AS-SDN-CLINIC-LAB	345	89	5,363	Yes	0

Name

Database

ASNs

Sets

Route objects

AS9136 in it

Not covered

RIPE::AS-WOBCOM

RIPElists itself further down2 member sets in no database: AS-PBB, AS-SDN-CLINIC-LAB

345

5,363

Yes

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.

AS-SET: missing member2
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
AS-SET: missing member	RIPE::AS-WOBCOM	AS-WOBCOM (RIPE) lists AS-PBB; no IRR database read has it.
AS-SET: missing member	RIPE::AS-WOBCOM	AS-WOBCOM (RIPE) lists AS-SDN-CLINIC-LAB; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

RIPE::AS-WOBCOM

AS-WOBCOM (RIPE) lists AS-PBB; no IRR database read has it.

AS-SET: missing member

RIPE::AS-WOBCOM

AS-WOBCOM (RIPE) lists AS-SDN-CLINIC-LAB; no IRR database read has it.

Route objects not announced

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


2a01:581:10::/48	RIPE	Valid

2a01:581:10::/48

RIPE

Valid

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.