Skip to main content

AS41357

UK-34SP-AS

34SP.com Limited

Registry

Authoritative registration data

AS number
41357
Name
UK-34SP-AS
Organisation
34SP.com Limited
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS41357
80.82.112.0/20 IPv4 /20 not checked
46.183.8.0/21 IPv4 /21 not checked
64.38.96.0/21 IPv4 /21 not checked
185.114.96.0/22 IPv4 /22 not checked
2a00:1ee0::/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 AS41357
Address families
LINX Manchester 1,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 AS41357 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS41357 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 125 638
v4 v6
AS174 COGENT-174 104 495
v4 v6
AS6939 HURRICANE 82 173
v4 v6
AS4455 BSO 1 5
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS41357 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 45
v4 v6
AS36236 NETACTUATE 1 5
v4 v6
AS13237 LAMBDANET-AS 1 4
v4

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.