bgpreport

Network · data from 2026-11-12

AS42306 Edera Group

Registry name: EDERA_Group CEZNET s.r.o., CZ · PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No 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 AS42306, seen from no peer

Announced routes

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

37.44.208.0/22 No ROA RIR databaseRIPE 672 100% 67
46.253.96.0/21 No ROA RIR databaseRIPE 672 100% 67
46.253.104.0/21 No ROA RIR databaseRIPE 672 100% 67
93.89.144.0/20 No ROA RIR databaseRIPE 672 100% 67
176.123.12.0/22 No ROA RIR databaseRIPE 672 100% 67
185.134.160.0/22 No ROA RIR databaseRIPE 672 100% 67
185.137.144.0/22 No ROA RIR databaseRIPE 672 100% 67
77.236.192.0/19 No ROA RIR databaseRIPE 669 99% 67
2a03:f280::/29 No ROA RIR databaseRIPE 633 100% 67
2a06:ed40::/29 No ROA RIR databaseRIPE 633 100% 67
2a07:4c0::/29 No ROA RIR databaseRIPE 633 100% 67
2a0e:5340::/29 No ROA RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS42306: AS42306:AS-EDERA. 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 (AS42306 isn't in the set, or no route object for AS42306 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 objectsAS42306 in itNot covered
AS42306:AS-EDERA RIPE 8136 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: none12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none37.44.208.0/22No ROA covers it. Add a ROA for AS42306, maxLength 22.672 of 673
ROA: none46.253.96.0/21No ROA covers it. Add a ROA for AS42306, maxLength 21.672 of 673
ROA: none46.253.104.0/21No ROA covers it. Add a ROA for AS42306, maxLength 21.672 of 673
ROA: none93.89.144.0/20No ROA covers it. Add a ROA for AS42306, maxLength 20.672 of 673
ROA: none176.123.12.0/22No ROA covers it. Add a ROA for AS42306, maxLength 22.672 of 673
ROA: none185.134.160.0/22No ROA covers it. Add a ROA for AS42306, maxLength 22.672 of 673
ROA: none185.137.144.0/22No ROA covers it. Add a ROA for AS42306, maxLength 22.672 of 673
ROA: none77.236.192.0/19No ROA covers it. Add a ROA for AS42306, maxLength 19.669 of 673
ROA: none2a03:f280::/29No ROA covers it. Add a ROA for AS42306, maxLength 29.633 of 636
ROA: none2a06:ed40::/29No ROA covers it. Add a ROA for AS42306, maxLength 29.633 of 636
ROA: none2a07:4c0::/29No ROA covers it. Add a ROA for AS42306, maxLength 29.633 of 636
ROA: none2a0e:5340::/29No ROA covers it. Add a ROA for AS42306, maxLength 29.633 of 636

Route objects not announced

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

2a03:f280::/32RIPENo 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.