Skip to main content

AS203752

E-CAPS

E-CAPS.net

Registry

Authoritative registration data

AS number
203752
Name
E-CAPS
Organisation
E-CAPS.net
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS203752
185.125.60.0/22 IPv4 /22 not checked
2a03:94a0::/32 IPv6 /32 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 AS203752
Address families
VIX 10,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 AS203752 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS203752 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 86 116
v4 v6
AS44306 Omonia 52 75
v4 v6
AS1299 TWELVE99 34 46
v4 v6
AS174 COGENT-174 34 44
v4 v6
AS15958 CETIN_doo_AS 15 23
v4 v6
AS48362 TKSWF-AS 2 6
v4 v6
AS9002 RETN-AS 2 5
v6
AS6663 TTI-NET 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203752 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

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 4
v4 v6
AS13030 INIT7 1 4
v4 v6
AS47692 NESSUS 1 4
v4 v6
AS51184 FONIRA 1 4
v4 v6
AS47147 AS-ANX 1 3
v4 v6
AS6720 MAGWIEN 1 2
v4 v6
AS31510 IKB-AS 1 2
v4 v6
AS34288 AS34288 1 2
v4 v6
AS35369 LINZAG-TELEKOM-AS 1 2
v4 v6
AS40994 Alwyzon 1 2
v4 v6
AS49544 i3Dnet 1 2
v4 v6
AS59890 Kabel-TV-Lampert 1 2
v4 v6
AS215628 AS-XENOX-AT 1 2
v4 v6

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.