Skip to main content

AS51744

ASJABLONKA

--- SuperNetwork ---

Registry

Authoritative registration data

AS number
51744
Name
ASJABLONKA
Organisation
--- SuperNetwork ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS51744
91.219.244.0/22 IPv4 /22 not checked
2001:67c:1798::/48 IPv6 /48 RPKI not found

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 AS51744
Address families
Peering.cz 20,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 AS51744 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS51744 in AS paths

Observed upstreams
Families
AS15935 HA-VEL-LOCAL-AS 348 430
v4 v6
AS39392 SuperNetwork 253 339
v4 v6
AS6939 HURRICANE 110 133
v4 v6
AS14840 ASN14840 8 20
v4 v6
AS1764 NEXTLAYER-AS 7 9
v4 v6
AS6204 ZET-NET 3 3
v4
AS6663 TTI-NET 3 3
v4
AS13194 BITE 3 3
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS51744 in AS paths

Observed downstreams
Families
AS206468 TREBORADICENET-AS 241 333
v4 v6
AS57069 ASDCC 144 170
v4
AS205026 WVG-CLOUD-AS 143 169
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 5 17
v4 v6
AS47692 NESSUS 5 12
v4 v6
AS51184 FONIRA 4 10
v4 v6
AS37721 ORG-VTS1-AFRINIC 5 6
v4 v6
AS59890 Kabel-TV-Lampert 5 6
v4 v6
AS49544 i3Dnet 4 5
v4 v6
AS29504 LBCFREE 3 5
v4 v6
AS35369 LINZAG-TELEKOM-AS 4 4
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.