Skip to main content

AS197936

ADB-AS

ORG-APsz4-RIPE

Registry

Authoritative registration data

AS number
197936
Name
ADB-AS
Organisation
ORG-APsz4-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS197936
91.230.58.0/23 IPv4 /23 not checked
149.5.177.0/24 IPv4 /24 not checked
91.230.58.0/24 IPv4 /24 not checked
91.230.59.0/24 IPv4 /24 not checked
2001:67c:2fc4::/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 AS197936 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS197936 in AS paths

Observed upstreams
Families
AS174 COGENT-174 157 502
v4 v6
AS12912 TMPL 116 266
v4 v6
AS6939 HURRICANE 40 68
v4 v6
AS29632 NASSIST-AS 2 2
v6
AS201054 EPIX-PolMix 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS197936 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 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.