Skip to main content

AS52153

BGCOM

ORG-NRaA1-RIPE

Registry

Authoritative registration data

AS number
52153
Name
BGCOM
Organisation
ORG-NRaA1-RIPE
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 AS52153
91.222.192.0/22 IPv4 /22 not checked
91.222.192.0/24 IPv4 /24 not checked
91.222.193.0/24 IPv4 /24 not checked
91.222.194.0/24 IPv4 /24 not checked
91.222.195.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

Internet Exchange memberships listed for AS52153
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Poznan 10,000 Mbps IPv4
EPIX.Warszawa 5,000 Mbps IPv4
IX.LODZ.PL: LAN 1 1,000 Mbps IPv4
WRIX: WRIX 10,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 AS52153 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS52153 in AS paths

Observed upstreams
Families
AS212261 441 1,265
v4
AS2914 NTT-DATA-2914 254 816
v4
AS3356 LEVEL3 236 405
v4
AS9002 RETN-AS 59 285
v4
AS201054 64 160
v4
AS5526 GENERACJApl-WR-IX-Exchange-Point 37 124
v4

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS52153 in AS paths

Observed downstreams
Families
AS38923 469 1,338
v4
AS44855 260 334
v4
AS57875 84 118
v4
AS200534 1 6
v4
AS31106 2 3
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 96
v4
AS49544 i3Dnet 4 20
v4
AS36236 NETACTUATE 1 1
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.