Skip to main content

AS44002

SYS-DATACOM

Czech Republic

Registry

Authoritative registration data

AS number
44002
Name
SYS-DATACOM
Organisation
Czech Republic
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

34

Total announced

47

Announced prefixes

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

Prefixes announced by AS44002
79.98.72.0/21 IPv4 /21 not checked
185.4.200.0/22 IPv4 /22 not checked
185.4.200.0/24 IPv4 /24 RPKI valid
185.4.202.0/24 IPv4 /24 RPKI valid
185.4.203.0/24 IPv4 /24 RPKI valid
79.98.72.0/24 IPv4 /24 not checked
79.98.73.0/24 IPv4 /24 not checked
79.98.74.0/24 IPv4 /24 not checked
79.98.75.0/24 IPv4 /24 RPKI valid
79.98.76.0/24 IPv4 /24 not checked
79.98.77.0/24 IPv4 /24 RPKI valid
79.98.78.0/24 IPv4 /24 RPKI valid
79.98.79.0/24 IPv4 /24 RPKI valid
2a02:970::/32 IPv6 /32 RPKI valid
2a02:970:1017::/48 IPv6 /48 RPKI valid
2a02:970:1019::/48 IPv6 /48 RPKI valid
2a02:970:1028::/48 IPv6 /48 not checked
2a02:970:1052::/48 IPv6 /48 RPKI valid
2a02:970:1061::/48 IPv6 /48 not checked
2a02:970:1068::/48 IPv6 /48 not checked
2a02:970:1078::/48 IPv6 /48 RPKI valid
2a02:970:1159::/48 IPv6 /48 RPKI valid
2a02:970:1176::/48 IPv6 /48 RPKI valid
2a02:970:1179::/48 IPv6 /48 not checked
2a02:970:1192::/48 IPv6 /48 not checked
2a02:970:1208::/48 IPv6 /48 RPKI valid
2a02:970:1243::/48 IPv6 /48 not checked
2a02:970:1245::/48 IPv6 /48 not checked
2a02:970:1248::/48 IPv6 /48 RPKI valid
2a02:970:1288::/48 IPv6 /48 not checked
2a02:970:1353::/48 IPv6 /48 not checked
2a02:970:1365::/48 IPv6 /48 RPKI valid
2a02:970:1366::/48 IPv6 /48 not checked
2a02:970:1384::/48 IPv6 /48 RPKI valid
2a02:970:1397::/48 IPv6 /48 RPKI valid
2a02:970:1399::/48 IPv6 /48 RPKI valid
2a02:970:1405::/48 IPv6 /48 not checked
2a02:970:1406::/48 IPv6 /48 RPKI valid
2a02:970:1446::/48 IPv6 /48 RPKI valid
2a02:970:1447::/48 IPv6 /48 RPKI valid
2a02:970:1448::/48 IPv6 /48 RPKI valid
2a02:970:1450::/48 IPv6 /48 not checked
2a02:970:1531::/48 IPv6 /48 RPKI valid
2a02:970:1532::/48 IPv6 /48 RPKI valid
2a02:970:1533::/48 IPv6 /48 RPKI valid
2a02:970:1724::/48 IPv6 /48 RPKI valid
2a02:970:3280::/48 IPv6 /48 RPKI valid

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 AS44002
Address families
Peering.cz 20,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 AS44002 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS44002 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 178 3,097
v4 v6
AS6939 HURRICANE 52 1,765
v4 v6
AS47232 ISPAlliance 264 1,408
v4 v6
AS14840 ASN14840 2 180
v4 v6
AS1764 NEXTLAYER-AS 4 157
v4 v6
AS22356 ASN22356 8 119
v4 v6
AS50629 LWLCOM 3 40
v4 v6
AS6204 ZET-NET 1 12
v4
AS6663 TTI-NET 1 12
v4
AS13194 BITE 1 12
v4
AS20562 OPEN-PEERING-AS 1 12
v4
AS263444 ASN263444 1 12
v4
AS44066 DE-FIRSTCOLO 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS44002 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 227
v4 v6
AS51184 FONIRA 1 92
v4 v6
AS29504 LBCFREE 1 46
v4 v6
AS49544 i3Dnet 1 46
v4 v6
AS59890 Kabel-TV-Lampert 1 46
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 45
v4 v6
AS47692 NESSUS 1 24
v4
AS35369 LINZAG-TELEKOM-AS 1 12
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.