Skip to main content

AS48602

CONNECTPLUS

Connect plus s.r.o.

Registry

Authoritative registration data

AS number
48602
Name
CONNECTPLUS
Organisation
Connect plus s.r.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS48602
185.140.244.0/24 IPv4 /24 not checked
185.140.245.0/24 IPv4 /24 not checked
185.140.246.0/24 IPv4 /24 not checked
185.140.247.0/24 IPv4 /24 not checked
2a07:20c0::/29 IPv6 /29 RPKI not found

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 AS48602
Address families
NIX.CZ: Public peering VLAN 10,000 Mbps IPv4 · IPv6
Peering.cz 20,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 AS48602 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS48602 in AS paths

Observed upstreams
Families
AS39392 SuperNetwork 369 1,349
v4 v6
AS6939 HURRICANE 27 120
v4
AS22356 ASN22356 5 20
v4
AS1764 NEXTLAYER-AS 3 20
v4
AS14840 ASN14840 2 20
v4
AS20562 OPEN-PEERING-AS 3 12
v4
AS41327 FIBERTELECOM-AS 2 8
v4
AS4455 BSO 1 4
v4
AS6204 ZET-NET 1 4
v4
AS6663 TTI-NET 1 4
v4
AS13194 BITE 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS48602 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

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.