Skip to main content

AS215085

PixelHosting

==================================================================

Registry

Authoritative registration data

AS number
215085
Name
PixelHosting
Organisation
==================================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS215085
83.142.31.0/24 IPv4 /24 not checked
2a06:9f41::/32 IPv6 /32 RPKI valid
2a06:9f46::/32 IPv6 /32 RPKI valid
2a06:9f41:a::/48 IPv6 /48 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 AS215085
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
ENS-IX 20,000 Mbps IPv4 · IPv6
ERA-IX Amsterdam 10,000 Mbps IPv4 · IPv6
NL-ix: Main 100 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 AS215085 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

47 networks seen before AS215085 in AS paths

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS215085 in AS paths

Observed downstreams
Families
AS47816 WKHB-AS2 383 570
v4 v6
AS207682 Maik-Polman 223 558
v6
AS202585 bgp-rodeo 219 534
v4 v6
AS214723 HEIJKOOP-AS 36 177
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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