161.36.104.0/24

Currently announced jointly by AS12244 SUPREME - Securitas Electronic Security, Inc., AS394135 Securitas Electronic Security, Inc., in the routed prefix 161.36.104.0/24.

Current ASN: AS12244 AS394135; SUPREME - Securitas Electronic Security, Inc.
Routed prefix: 161.36.104.0/24; Most specific route covering this prefix
ASNs over time: 2; 2 announcement records
RIR allocation: ARIN; United States · 161.36.104.0/21

Routing data · Oct 24, 2026, 06:23 UTC

ASN historyEvery routed prefix covering 161.36.104.0/24

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
161.36.104.0/24	AS12244	SUPREME - Securitas Electronic Security, Inc.	United States	2026-10-23 22:19	2026-10-24 06:23	Announcing
161.36.104.0/24	AS394135	Securitas Electronic Security, Inc.	United States	Before monitoring	2026-10-24 06:23	Announcing

More specific routes0 total

No more specific routes inside this prefix.

Change logAll changes

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-10-23 22:19	161.36.104.0/24	Origin added	AS12244	SUPREME - Securitas Electronic Security, Inc.	AS394135	United States

Look up another address

RIR allocation record

Registry: ARIN
Allocated block: 161.36.104.0/21
Country: United States
Allocation date: 1992-05-14
Status: allocated

From the RIRs’ delegated statistics files. Shows where the addresses are registered, not where they are used.

How monitoring works

Every 2 hours ASNBase takes the bgp.tools global routing table (prefix → origin ASN) and compares it with the previous one. The detected time is the time of that comparison; the actual change can be up to about 2 hours earlier.
Only routes seen by more than 100 bgp.tools peers are listed as changes; routes with less visibility are only kept in the history.
A new announcement counts only if it is still in the next routing table, and a withdrawal only if the prefix is missing from two tables in a row, so short flaps are ignored.
ASNBase has been monitoring since 2026-10-19. “Before monitoring” under “First seen” means the route was already announced when monitoring started; the earlier date is unknown.
Prefixes first seen during the first day of monitoring do not count as new announcements: most of them were simply missing from the table at the moment monitoring started.
Countries and regions follow the ASN’s registration, not the actual location of the IP addresses.