bgpreport

Network · data from 2026-11-12

AS12348 ODN OnlineDienst Nordbayern GmbH & Co. KG

Registry name: AS12348 ODN OnlineDienst Nordbayern GmbH & Co. KG, DE · PeeringDB

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

Announced routes

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

86.109.224.0/19 No ROA RIR databaseRIPE 672 100% 66
91.213.20.0/24 No ROA RIR databaseRIPE 672 100% 66
212.34.160.0/19 No ROA RIR databaseRIPE 672 100% 66
2001:67c:2e60::/48 No ROA RIR databaseRIPE 636 100% 67
212.34.161.0/24 Valid Nonecovered by 212.34.160.0/19 672 100% 66
212.34.162.0/24 Valid Nonecovered by 212.34.160.0/19 669 99% 66
86.109.224.0/24 Valid Nonecovered by 86.109.224.0/19 4 1%low visibility 3
193.23.167.0/24 Valid RIR databaseRIPE 672 100% 66
2a00:12e8:f141::/48 Valid RIR databaseRIPE 636 100% 67
2a01:120::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS12348: AS-ODNDE. 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 (AS12348 isn't in the set, or no route object for AS12348 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 objectsAS12348 in itNot covered
AS-ODNDE RIPE 51115 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 13 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none86.109.224.0/19No ROA covers it. Add a ROA for AS12348, maxLength 19.672 of 673
ROA: none91.213.20.0/24No ROA covers it. Add a ROA for AS12348, maxLength 24.672 of 673
ROA: none212.34.160.0/19No ROA covers it. Add a ROA for AS12348, maxLength 19.672 of 673
ROA: none2001:67c:2e60::/48No ROA covers it. Add a ROA for AS12348, maxLength 48.636 of 636
Route object: none212.34.161.0/24No route object for it. A route object for 212.34.160.0/19 with origin AS12348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12348 in the RIR database for the space.672 of 673
Route object: none212.34.162.0/24No route object for it. A route object for 212.34.160.0/19 with origin AS12348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12348 in the RIR database for the space.669 of 673
Route object: none86.109.224.0/24No route object for it. A route object for 86.109.224.0/19 with origin AS12348 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12348 in the RIR database for the space.4 of 673

Route objects not announced

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

86.109.228.0/24RIPENo ROA
86.109.248.0/23RIPEInvalid: origin
194.45.232.0/24RIPENo ROA
194.173.174.0/23RIPENo ROA
212.34.172.0/24RIPENo ROA
212.34.177.0/24RIPENo 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.