Skip to main content

AS30528

EICAT

E. I. Catalyst

Registry

Authoritative registration data

AS number
30528
Name
EICAT
Organisation
E. I. Catalyst
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS30528
66.96.16.0/20 IPv4 /20 not checked
72.0.64.0/20 IPv4 /20 not checked
205.189.139.0/24 IPv4 /24 not checked
2001:1928::/32 IPv6 /32 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 AS30528
Address families
TorIX 1,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 AS30528 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS30528 in AS paths

Observed upstreams
Families
AS7311 FRONTIER 300 1,267
v4 v6
AS835 47 207
v4 v6
AS394256 CLOUDSINGULARITY 1 4
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS30528 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4 v6
AS49544 i3Dnet 1 8
v4 v6
AS1828 UNITAS 1 4
v4 v6
AS22652 1 4
v4 v6
AS36236 NETACTUATE 1 4
v4 v6
AS35280 F5 1 3
v4
AS1403 1 2
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.