Skip to main content

AS209252

PGLESPORTS-MAIN

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

Registry

Authoritative registration data

AS number
209252
Name
PGLESPORTS-MAIN
Organisation
+----------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS209252
185.62.206.0/24 IPv4 /24 not checked
85.208.28.0/24 IPv4 /24 not checked
85.208.30.0/24 IPv4 /24 not checked
85.208.31.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS209252 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS209252 in AS paths

Observed upstreams
Families
AS5405 INTERDOTLINK 255 759
v4
AS6939 HURRICANE 134 188
v4
AS3223 VOXILITY 127 171
v4
AS1299 TWELVE99 61 156
v4
AS9002 RETN-AS 89 119
v4
AS20722 ALLNET-AS 12 16
v4
AS35280 F5 4 8
v4
AS39351 ESAB-AS 2 4
v4
AS50304 BLIX 2 4
v4
AS31500 GNM-AS 1 2
v4
AS33891 CORE-BACKBONE 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS209252 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4
AS49544 i3Dnet 1 4
v4
AS35598 INETCOM 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS42473 AS-ANEXIA 1 2
v4
AS42541 FIBERBY 1 2
v4
AS199524 GCORE 1 2
v4
AS205206 Netsite 1 2
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.