Skip to main content

AS56504

HOSTCIRCLE-L-NL

HostCircle B.V.

Registry

Authoritative registration data

AS number
56504
Name
HOSTCIRCLE-L-NL
Organisation
HostCircle B.V.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS56504
110.44.4.0/24 IPv4 /24 RPKI not found
154.21.215.0/24 IPv4 /24 not checked
178.237.56.0/24 IPv4 /24 not checked
178.237.57.0/24 IPv4 /24 RPKI valid
178.237.58.0/24 IPv4 /24 RPKI valid
178.237.59.0/24 IPv4 /24 RPKI valid
193.91.11.0/24 IPv4 /24 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 AS56504
Address families
FogIXP Amsterdam 10,000 Mbps IPv4 · IPv6
Frys-IX 100,000 Mbps IPv4 · IPv6
INTERIX 100,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 AS56504 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS56504 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS56504 in AS paths

Observed downstreams
Families
AS47674 NETSOLUTIONS 93 2,787
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 25
v4
AS34927 iFog-GmbH 1 10
v4
AS3399 OBE-NET 1 5
v4
AS24961 MYLOC-AS 1 5
v4
AS34019 HIVANE 1 5
v4
AS37721 ORG-VTS1-AFRINIC 1 5
v4
AS49544 i3Dnet 1 5
v4
AS263152 ASN263152 1 5
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.