157.228.158.0/23

No announcement in the global routing table covers this address right now.

Routing data · Nov 1, 2026, 18:24 UTC

ASN historyEvery routed prefix covering 157.228.158.0/23

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
157.228.158.0/23	AS209657	Svinin Mihail Yurievich, UpStreams	Russia	2026-10-20 18:21	2026-10-31 20:25	Stopped

Prefix	ASN	Name	Registered country	First seen (UTC)	Last seen (UTC)	Status
157.228.158.0/24	AS209657	Svinin Mihail Yurievich, UpStreams	Russia	2026-10-20 18:21	2026-10-27 12:20	Stopped
157.228.159.0/24	AS209657	Svinin Mihail Yurievich, UpStreams	Russia	2026-10-20 18:21	2026-10-27 16:20	Stopped

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
2026-10-31 22:25	157.228.158.0/23	Withdrawal	AS209657	Svinin Mihail Yurievich, UpStreams	—	Russia
2026-10-30 22:21	157.228.158.0/23	Withdrawal	AS209657	Svinin Mihail Yurievich, UpStreams	—	Russia
2026-10-30 02:20	157.228.158.0/23	Withdrawal	AS209657	Svinin Mihail Yurievich, UpStreams	—	Russia
2026-10-27 14:20	157.228.158.0/23	Withdrawal	AS209657	Svinin Mihail Yurievich, UpStreams	—	Russia

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

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.