Skip to main content

AS41782

BGLAN-AS

BGLAN LTD

Registry

Authoritative registration data

AS number
41782
Name
BGLAN-AS
Organisation
BGLAN LTD
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 AS41782
193.84.103.0/24 IPv4 /24 not checked
84.38.243.0/24 IPv4 /24 not checked
85.196.168.0/24 IPv4 /24 not checked
85.196.169.0/24 IPv4 /24 not checked
91.216.57.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 AS41782 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS41782 in AS paths

Observed upstreams
Families
AS35761 124 750
v4
AS34224 NETERRA-AS 107 668
v4
AS57463 44 250
v4
AS34019 HIVANE 4 30
v4
AS34549 MEER-AS 3 20
v4
AS25091 IP-Max 2 20
v4
AS39351 ESAB-AS 2 10
v4
AS9044 1 10
v4
AS49434 2 8
v4
AS50673 1 5
v4
AS58057 SECUREBIT 1 5
v4
AS137409 GSLNETWORKS-AS-AP 1 5
v4
AS401753 1 5
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS41782 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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