Skip to main content

AS5564

SOL-AS

Commercial internet service provider

Registry

Authoritative registration data

AS number
5564
Name
SOL-AS
Organisation
Commercial internet service provider
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS5564
194.247.64.0/19 IPv4 /19 RPKI valid
213.128.224.0/19 IPv4 /19 RPKI valid
194.247.89.0/24 IPv4 /24 RPKI valid
194.247.94.0/24 IPv4 /24 RPKI valid
213.128.253.0/24 IPv4 /24 RPKI valid
213.128.254.0/24 IPv4 /24 not checked
2a00:5580::/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 AS5564
Address families
LINX LON1: Main 10,000 Mbps IPv4 · IPv6
LINX LON2 1,000 Mbps IPv4 · IPv6
LINX Scotland: LINX Scotland 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 AS5564 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

28 networks seen before AS5564 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS5564 in AS paths

Observed downstreams
Families
AS208564 bedroq 211 282
v4
AS6939 HURRICANE 43 64
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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