bgpreport

Network · data from 2026-11-12

AS60266 EMBEDIT-AS EmbedIT s.r.o.

Registry name: EMBEDIT-AS EmbedIT s.r.o., CZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60266, 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.
2a00:cb20::/43 Invalid: maxLength Nonecovered by 2a00:cb20::/32 61 10%low visibility 29
2a00:cb20:111a::/48 Invalid: maxLength Nonecovered by 2a00:cb20:1100::/40 61 10%low visibility 29
2a00:cb20:111b::/48 Invalid: maxLength Nonecovered by 2a00:cb20:1100::/40 61 10%low visibility 29
2a00:cb20:111e::/48 Invalid: maxLength Nonecovered by 2a00:cb20:1100::/40 61 10%low visibility 29
185.33.157.0/24 Valid RIR databaseRIPE 673 100% 66
185.33.159.0/24 Valid RIR databaseRIPE 673 100% 66
2a00:cb20::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS60266 isn't in PeeringDB, where networks name their AS-SET.

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 11 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a00:cb20::/43ROA 2a00:cb20::/32 AS60266 has maxLength 32; the route is a /43. Raise the maxLength, or add a ROA for 2a00:cb20::/43.61 of 636
Route object: none2a00:cb20::/43No route object for it. A route object for 2a00:cb20::/32 with origin AS60266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60266 in the RIR database for the space.61 of 636
ROA: maxLength2a00:cb20:111a::/48ROA 2a00:cb20::/32 AS60266 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a00:cb20:111a::/48.61 of 636
Route object: none2a00:cb20:111a::/48No route object for it. A route object for 2a00:cb20:1100::/40 with origin AS60266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60266 in the RIR database for the space.61 of 636
ROA: maxLength2a00:cb20:111b::/48ROA 2a00:cb20::/32 AS60266 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a00:cb20:111b::/48.61 of 636
Route object: none2a00:cb20:111b::/48No route object for it. A route object for 2a00:cb20:1100::/40 with origin AS60266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60266 in the RIR database for the space.61 of 636
ROA: maxLength2a00:cb20:111e::/48ROA 2a00:cb20::/32 AS60266 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a00:cb20:111e::/48.61 of 636
Route object: none2a00:cb20:111e::/48No route object for it. A route object for 2a00:cb20:1100::/40 with origin AS60266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60266 in the RIR database for the space.61 of 636

Route objects not announced

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

2a00:cb20:1100::/40RIPEInvalid: maxLength
2a00:cb20:2100::/40RIPEInvalid: maxLength
2a00:cb20:3b00::/40RIPEInvalid: maxLength

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.