Skip to main content

AS48559

INFOMEX-AS

*** EPIX ***

Registry

Authoritative registration data

AS number
48559
Name
INFOMEX-AS
Organisation
*** EPIX ***
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS48559
185.27.52.0/22 IPv4 /22 not checked
195.248.226.0/23 IPv4 /23 not checked
195.26.12.0/23 IPv4 /23 not checked
91.224.214.0/23 IPv4 /23 not checked
91.213.108.0/24 IPv4 /24 not checked
2a00:9320:fffd::/48 IPv6 /48 not checked
2a00:9320:fffe::/48 IPv6 /48 not checked
2a00:9320:ffff::/48 IPv6 /48 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 AS48559
Address families
EPIX.Katowice 10,000 Mbps IPv4
Equinix Warsaw 1,000 Mbps IPv4
TPIX PL 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 AS48559 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS48559 in AS paths

Observed upstreams
Families
AS29535 690 2,676
v4 v6
AS3356 LEVEL3 75 487
v4
AS20804 ASN-TELENERGO 50 132
v4
AS50607 11 27
v4
AS6204 1 5
v4
AS24115 ASN-EQIX-MLPE 3 3
v4
AS201054 EPIX-PolMix 1 3
v6
AS35320 1 1
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS48559 in AS paths

Observed downstreams
Families
AS197279 275 379
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 27
v4 v6
AS49544 i3Dnet 2 18
v4 v6
AS28917 Fiord-AS 1 5
v4
AS36236 NETACTUATE 1 1
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.