Skip to main content

AS48683

BI-LINK-AS

Bilink LLC

Registry

Authoritative registration data

AS number
48683
Name
BI-LINK-AS
Organisation
Bilink LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS48683
176.105.0.0/17 IPv4 /17 not checked
213.111.64.0/18 IPv4 /18 not checked
2001:67c:2534::/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

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 AS48683 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS48683 in AS paths

Observed upstreams
Families
AS1820 WNET 604 1,157
v4 v6
AS43139 MAXIMUMA-AS 67 158
v4
AS6939 HURRICANE 14 30
v4
AS14840 ASN14840 2 10
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS48683 in AS paths

Observed downstreams
Families
AS58032 Fortunat-AS 274 347
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 16
v4
AS49544 i3Dnet 1 4
v4
AS212483 level86 1 4
v4
AS48919 UA-CITY-AS 1 2
v4
AS59514 DARNYTSIA-NET 1 2
v4
AS198150 SIACOM-AS 1 2
v4
AS209823 ENKI-AS 1 2
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.