Skip to main content

AS51528

CENTR-AS

================================= EXPRESS

Registry

Authoritative registration data

AS number
51528
Name
CENTR-AS
Organisation
================================= EXPRESS
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS51528
91.219.52.0/22 IPv4 /22 not checked
91.219.52.0/23 IPv4 /23 not checked
91.219.54.0/23 IPv4 /23 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 AS51528 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS51528 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 826 1,053
v4
AS6939 HURRICANE 28 80
v4
AS50581 UTG 25 62
v4
AS24482 SGGS-AS-AP 2 35
v4
AS14840 ASN14840 2 15
v4
AS56386 6 9
v4
AS22356 4 8
v4
AS6663 TTI-NET 1 3
v4
AS13194 BITE 1 3
v4
AS263444 1 3
v4
AS39120 1 2
v4

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS51528 in AS paths

Observed downstreams
Families
AS198030 220 277
v4
AS51279 215 271
v4
AS197251 166 228
v4
AS15738 UAEXPRESS 6 9
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS212483 level86 1 6
v4
AS48919 1 3
v4
AS198150 SIACOM-AS 1 3
v4
AS209823 ENKI-AS 1 3
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.