Skip to main content

AS51484

BLOKOWE

Sieci Blokowe S.C.

Registry

Authoritative registration data

AS number
51484
Name
BLOKOWE
Organisation
Sieci Blokowe S.C.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS51484
46.45.64.0/18 IPv4 /18 not checked
46.45.112.0/20 IPv4 /20 not checked
46.45.80.0/20 IPv4 /20 not checked
46.45.96.0/20 IPv4 /20 not checked
46.45.104.0/23 IPv4 /23 not checked
2a03:24c0::/48 IPv6 /48 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 AS51484
Address families
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6
Equinix Warsaw 10,000 Mbps IPv4
IX.LODZ.PL: LAN 1 10,000 Mbps IPv4
THINX Warsaw 10,000 Mbps IPv4 · IPv6
TPIX PL 20,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 AS51484 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS51484 in AS paths

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS51484 in AS paths

Observed downstreams
Families
AS208066 556 2,743
v4 v6
AS206518 340 1,027
v4
AS44856 269 686
v4
AS201342 237 302
v4
AS201091 64 165
v4

No rows match “”.

Showing of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 110
v4 v6
AS49544 i3Dnet 4 28
v4 v6
AS36236 NETACTUATE 4 11
v4 v6
AS28917 Fiord-AS 3 11
v4
AS212483 level86 2 4
v6
AS198150 SIACOM-AS 2 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.