Skip to main content

AS60670

WideFM-LTD

WideFM Ltd

Registry

Authoritative registration data

AS number
60670
Name
WideFM-LTD
Organisation
WideFM Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS60670
185.180.184.0/24 IPv4 /24 not checked
185.180.185.0/24 IPv4 /24 not checked
185.180.186.0/24 IPv4 /24 not checked
185.180.187.0/24 IPv4 /24 not checked
45.155.108.0/24 IPv4 /24 not checked
45.155.109.0/24 IPv4 /24 not checked
45.155.110.0/24 IPv4 /24 not checked
45.155.111.0/24 IPv4 /24 not checked
62.68.95.0/24 IPv4 /24 not checked
2a0a:ad80::/29 IPv6 /29 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 AS60670
Address families
LINX LON1: Main 10,000 Mbps IPv4
LINX LON2 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 AS60670 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

45 networks seen before AS60670 in AS paths

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS60670 in AS paths

Observed downstreams
Families
AS50468 417 880
v4
AS196745 DATACENTA-AS 33 322
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

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