Skip to main content

AS198951

BLS-AG

BLS AG

Registry

Authoritative registration data

AS number
198951
Name
BLS-AG
Organisation
BLS AG
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 AS198951
194.56.176.0/22 IPv4 /22 not checked
194.56.174.0/23 IPv4 /23 not checked
2001:678:518::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS198951 in AS paths

Observed upstreams
Families
AS15576 NTS 182 534
v4 v6
AS39040 NTSWorkspaceAG-AS39040 168 325
v4 v6
AS6939 HURRICANE 18 38
v4
AS34019 HIVANE 4 18
v4 v6
AS48362 TKSWF-AS 2 12
v4 v6
AS9002 RETN-AS 7 11
v6
AS47147 AS-ANX 2 11
v4 v6
AS39351 ESAB-AS 2 6
v4 v6
AS24961 MYLOC-AS 2 5
v4 v6
AS1764 NEXTLAYER-AS 1 3
v4 v6
AS1836 GREEN 1 3
v4 v6
AS34927 iFog-GmbH 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS198951 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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