Skip to main content

AS59699

LENFIBER-AS

Lenfiber

Registry

Authoritative registration data

AS number
59699
Name
LENFIBER-AS
Organisation
Lenfiber
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS59699
149.13.148.0/22 IPv4 /22 not checked
185.30.188.0/22 IPv4 /22 not checked
185.4.152.0/22 IPv4 /22 not checked
185.63.161.0/24 IPv4 /24 not checked
185.63.162.0/24 IPv4 /24 not checked
185.63.163.0/24 IPv4 /24 not checked
85.208.241.0/24 IPv4 /24 not checked
85.208.242.0/24 IPv4 /24 not checked

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 AS59699
Address families
MIX-IT 10,000 Mbps IPv4
TOP-IX: Public Peering VLAN 10,000 Mbps IPv4
VSIX: Primary 10,000 Mbps IPv4

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 AS59699 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS59699 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 1,080 2,971
v4
AS6762 SEABONE-NET 225 977
v4
AS6939 HURRICANE 109 296
v4
AS8218 NEO-ASN 6 98
v4
AS14840 ASN14840 2 35
v4
AS24961 MYLOC-AS 10 28
v4
AS50877 AIRBEAM-AS 10 21
v4
AS4455 2 21
v4
AS2593 5 14
v4
AS5405 INTERDOTLINK 2 14
v4
AS137409 GSLNETWORKS-AS-AP 2 14
v4
AS6204 1 7
v4
AS9009 M247 1 7
v4
AS60171 AFRIX-AS 1 7
v4
AS1267 2 2
v4
AS264409 1 2
v4
AS28716 RETELIT-AS 1 1
v4

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS59699 in AS paths

Observed downstreams
Families
AS201795 WBT-AS 263 1,008
v4
AS212282 264 337
v4
AS209345 263 336
v4
AS209646 263 336
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 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.