Skip to main content

AS214443

BEBYTE

Be Byte Srl

Registry

Authoritative registration data

AS number
214443
Name
BEBYTE
Organisation
Be Byte Srl
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS214443
217.61.242.0/23 IPv4 /23 RPKI valid
2a01:e600::/29 IPv6 /29 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS214443
Address families
MIX Thessaloniki 10,000 Mbps IPv4 · IPv6
MIX-IT 10,000 Mbps IPv4 · IPv6
Namex Rome: VLAN Peering 10,000 Mbps IPv4 · IPv6
PCIX 10,000 Mbps IPv4 · IPv6
VSIX: Primary 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS214443 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS214443 in AS paths

Observed upstreams
Families
AS6762 SEABONE-NET 309 600
v4 v6
AS47217 PLANETEL-SPA 150 286
v4 v6
AS6939 HURRICANE 118 184
v4 v6
AS8218 NEO-ASN 10 47
v4 v6
AS24482 SGGS-AS-AP 3 37
v4 v6
AS5405 INTERDOTLINK 14 26
v4 v6
AS14840 ASN14840 4 20
v4 v6
AS4455 BSO 4 10
v4 v6
AS29075 IELO 5 8
v4 v6
AS24961 MYLOC-AS 4 8
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 7
v4 v6
AS6204 ZET-NET 2 3
v4
AS9009 M247 2 3
v4
AS31543 MYNET-AS 2 3
v4
AS2593 ASN-VSIX 1 2
v4 v6
AS12735 ASTurkNet 1 2
v6
AS28716 RETELIT-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS214443 in AS paths

Observed downstreams
Families
AS210524 AS_TRASMINET 267 665
v4

No rows match “”.

Showing – of

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.