Skip to main content

AS5526

GENERACJApl-WR-IX-Exchange-Point

+------------------------------------------------

Registry

Authoritative registration data

AS number
5526
Name
GENERACJApl-WR-IX-Exchange-Point
Organisation
+------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS5526
Address families
1-PL FREE 10,000 Mbps IPv4 · IPv6
Equinix Warsaw 10,000 Mbps IPv4
THINX Warsaw 60,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 AS5526 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS5526 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 72 704
v4
AS24115 ASN-EQIX-MLPE 16 211
v4
AS24748 3 154
v4
AS137409 GSLNETWORKS-AS-AP 6 64
v4
AS9009 M247 1 7
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS5526 in AS paths

Observed downstreams
Families
AS29596 68 1,439
v4
AS52153 37 124
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 330
v4
AS49544 i3Dnet 3 62
v4
AS36236 NETACTUATE 2 31
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.