Network · data from 2026-11-12
AS214443 Be Byte S.R.L.
Registry name: BEBYTE BE BYTE SRL, IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214443, 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.
| 2a01:e601:1006::/48 | Invalid: maxLength | Nonecovered by 2a01:e601::/32 | 1 0%low visibility |
| 217.61.242.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 2a01:e600::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS214443: AS214443:AS-BEBYTE. 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 (AS214443 isn't in the set, or no route object for AS214443 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 | AS214443 in it | Not covered |
|---|---|---|---|---|---|
| AS214443:AS-BEBYTE | RIPE | 2 | 1 | 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 7 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2a01:e601:1006::/48 | ROA 2a01:e600::/29 AS214443 has maxLength 29; ROA 2a01:e601::/32 AS214443 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2a01:e601:1006::/48. |
| Route object: none | 2a01:e601:1006::/48 | No route object for it. A route object for 2a01:e601::/32 with origin AS214443 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214443 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214443 whose prefix no peer sees AS214443 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.136.241.0/24 | RIPE | Valid |
| 217.61.242.0/24 | RIPE | Valid |
| 217.61.243.0/24 | RIPE | Valid |
| 2a01:e600::/32 | RIPE | Valid |
| 2a01:e601::/32 | 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.