Skip to main content

AS202819

DATASYS

DATASYS - edoma.net s.r.o.

Registry

Authoritative registration data

AS number
202819
Name
DATASYS
Organisation
DATASYS - edoma.net s.r.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS202819
185.142.48.0/22 IPv4 /22 not checked
185.142.49.0/24 IPv4 /24 not checked
84.245.95.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 AS202819
Address families
SIX.SK 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 AS202819 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS202819 in AS paths

Observed upstreams
Families
AS5578 AS-BENESTRA 235 904
v4
AS6939 HURRICANE 18 54
v4
AS3303 SWISSCOM 6 21
v4
AS33891 CORE-BACKBONE 4 12
v4
AS6204 2 6
v4
AS1764 NEXTLAYER-AS 1 3
v4
AS6663 1 3
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS202819 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 21
v4
AS49544 i3Dnet 1 6
v4
AS40994 1 3
v4
AS44901 1 3
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.