Route changes on 2026-10-29

Changes found when comparing the global BGP routing table on 2026-10-29 (UTC): IP prefixes that moved to another ASN, were announced for the first time, gained an extra origin, or were withdrawn from the table.

Origin change: 4; That day · filtered
New announcement: 30; That day · filtered
Origin added: 3; That day · filtered
Withdrawal: 49; That day · filtered

Routing data · Nov 1, 2026, 20:20 UTC

Origin changeClear filters

CountryIP versionASN

Detected (UTC)	Prefix	Change	ASN	Name	Previous ASN	Country
14:19	89.16.32.0/19	Origin change	AS29554	Svyaznoy Chain SV	AS34485	Russia
14:19	83.143.192.0/21	Origin change	AS29554	Svyaznoy Chain SV	AS34485	Russia
14:19	185.139.108.0/22	Origin change	AS29554	Svyaznoy Chain SV	AS34485	Russia
06:23	217.60.27.0/24	Origin change	AS219506	TURTLEGUARD-CLOUD-AS	AS198584	Russia

By day

Origin change
New announcement
Origin added

Prefixes with a new ASN on each of the last 7 days, excluding withdrawals. Select a date to see all of that day’s changes. Another 291 changes are waiting for confirmation at the next comparison.

IP address ASN history

Enter an IP address or prefix to see which ASNs have announced the routes covering it.

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.