Skip to main content

AS200539

INTELLYSPJ-AS

INTELLY

Registry

Authoritative registration data

AS number
200539
Name
INTELLYSPJ-AS
Organisation
INTELLY
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

0

Total announced

13

Announced prefixes

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

Prefixes announced by AS200539
195.136.56.0/21 IPv4 /21 not checked
185.103.152.0/22 IPv4 /22 RPKI valid
185.239.12.0/22 IPv4 /22 RPKI valid
195.136.100.0/22 IPv4 /22 not checked
195.136.52.0/22 IPv4 /22 not checked
195.136.100.0/24 IPv4 /24 RPKI valid
195.136.101.0/24 IPv4 /24 RPKI valid
195.136.56.0/24 IPv4 /24 RPKI valid
195.136.57.0/24 IPv4 /24 RPKI valid
195.136.58.0/24 IPv4 /24 RPKI valid
195.136.59.0/24 IPv4 /24 not checked
195.136.60.0/24 IPv4 /24 RPKI valid
195.136.61.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

Internet Exchange memberships listed for AS200539
Address families
EPIX.Warszawa 10,000 Mbps IPv4
Equinix Warsaw 10,000 Mbps IPv4
TPIX PL — 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 AS200539 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS200539 in AS paths

Observed upstreams
Families
AS20804 ASN-TELENERGO 133 901
v4
AS3356 LEVEL3 119 734
v4
AS201054 EPIX-PolMix 40 501
v4
AS33891 CORE-BACKBONE 12 120
v4
AS137409 GSLNETWORKS-AS-AP 7 74
v4
AS20485 TRANSTELECOM 6 48
v4
AS9009 M247 1 8
v4
AS13194 BITE 1 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200539 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 26
v4
AS36236 NETACTUATE 2 13
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.