Skip to main content

AS51380

GREY-AS

--Downstrem--

Registry

Authoritative registration data

AS number
51380
Name
GREY-AS
Organisation
--Downstrem--
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS51380
195.20.4.0/23 IPv4 /23 not checked
195.20.5.0/24 IPv4 /24 not checked
195.20.6.0/24 IPv4 /24 not checked
91.218.192.0/24 IPv4 /24 not checked
91.218.193.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS51380 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS51380 in AS paths

Observed upstreams
Families
AS199995 OT-AS 264 1,223
v4
AS57455 105 438
v4
AS9002 RETN-AS 64 306
v4
AS8218 NEO-ASN 2 40
v4
AS47692 2 14
v4
AS48648 3 11
v4
AS39351 ESAB-AS 2 10
v4
AS49434 2 10
v4
AS9198 1 5
v4
AS15958 1 5
v4
AS42295 TBISS-AS 1 5
v4
AS60171 1 5
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS51380 in AS paths

Observed downstreams
Families
AS197263 152 192
v4

No rows match “”.

Showing of

Uncertain adjacencies

16 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.