Skip to main content

AS11588

LAMBDA-BB

Lambda

Registry

Authoritative registration data

AS number
11588
Name
LAMBDA-BB
Organisation
Lambda
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS11588
68.209.84.0/22 IPv4 /22 not checked
198.145.39.0/24 IPv4 /24 not checked
2607:bb40::/32 IPv6 /32 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 AS11588
Address families
CANIX Montreal 200,000 Mbps IPv4 · IPv6
ChIX 100,000 Mbps IPv4 · IPv6
KCIX 200,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 AS11588 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS11588 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 415 1,560
v4 v6
AS6461 ZAYO-6461 277 771
v4 v6
AS3356 LEVEL3 230 402
v4 v6
AS2914 NTT-DATA-2914 177 340
v4 v6
AS174 COGENT-174 124 152
v4
AS6939 HURRICANE 97 126
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS11588 in AS paths

Observed downstreams
Families
AS398090 803 2,357
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 6
v4 v6
AS36236 NETACTUATE 2 5
v4 v6
AS1003 ANDREWNET 2 4
v4 v6
AS1403 EBOX 2 4
v4 v6
AS34927 iFog-GmbH 2 2
v6
AS35280 F5 2 2
v4
AS200454 2 2
v6

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.