The UPX Platform now supports Telegram as a delivery channel for notifications, alongside existing options like Email, Slack, and ServiceNow. This means you can send alerts directly to your Telegram chats, groups, or channels.

What’s New

• Multiple delivery channels

  You can configure one or more Telegram channels under Notification Center → Delivery Channels. Each channel is defined by a Chat ID and a Channel Name, and works just like Slack or Email endpoints.

• Flexible assignments

  Once created, Telegram channels can be selected when editing any notification type in the platform. This lets you decide exactly which alerts should go where:

  • Send all critical alerts to a Telegram group.

  • Keep daily summaries in Email.

  • Route specific product events to Slack.

• Duplicate configurations

  To make things even easier, notification types can be duplicated. For example:

  • One configuration sends alerts + summaries to Telegram.

  • A duplicate sends only summaries to Email.

How it Works

1. Create a new delivery channel

   • Go to Notification Center → Delivery Channels → Add/Edit.

   • Select Telegram as the channel type.

   • Enter the Chat ID and Channel Name, then save.

2. Assign the delivery channel to notifications

   • Open the configuration for any notification type.

   • Under Delivery Channels, select one or more endpoints (Slack, Email, Telegram, ServiceNow).

   • Save the configuration.

   • Notifications will now be routed to the selected Telegram chat(s) along with any other chosen channels.

ASN Live has always been the place to answer “what’s happening this very second?” in your network. Connected to collectors across the globe, it streams BGP updates in real time, letting you see changes as they happen. With this new update, ASN Live becomes even more powerful and interactive.

The highlight of this release is the real-time terminal feed. Every new route announcement is now displayed line by line, showing the prefix, the full AS path, and the collector location where it was first observed. This gives engineers a direct, transparent view into the global propagation of their routes, as if watching the internet’s conversation unfold in real time.

On top of that, you can now pin prefixes directly from either the table or the terminal. Once pinned, a dedicated terminal opens up, focused exclusively on that prefix. This view shows not only live updates for the selected prefix but also a regional breakdown of path distribution, helping you immediately spot propagation patterns.

Each pinned view includes interactive percentage gauges that summarize path distribution. Clicking on a gauge lets you drill down into the exact AS paths behind the numbers, and filter them by ASN for deep troubleshooting. This makes it simple to pivot from high-level trends to low-level details in a couple of clicks.

Another new capability is the option to add prefixes that are not yet announced to your monitoring list in ASN Live. For example, you may configure a more specific prefix before making the actual announcements and then watch in real time as upstreams begin propagating the updates. This allows you to prepare monitoring in advance and confirm propagation the moment the change is activated.

We’ve also introduced a connection monitor at the top of the page. This indicator stays green while all collectors are active and the page is connected, giving you confidence that you’re seeing the full, live picture without needing to second-guess the feed.

Together, these updates make ASN Live the ideal tool for maintenance windows, incident response, and continuous monitoring. Whether you’re confirming new announcements, catching flapping routes in real time, or diagnosing routes that seem “stuck,” ASN Live gives you immediate visibility with global context.

We’ve improved the ASN Monitor to make resource validation more transparent.
From now on, if a prefix has multiple RPKI or IRR records and at least one of them is inconsistent, the system will display a yellow warning icon in the Resources area.

This means you’ll still see valid records as before, but you’ll also be alerted whenever conflicting or invalid records are present — helping you quickly identify and resolve potential issues.

Example: it’s common for a prefix to have more than one IRR entry. However, if one of these entries is tied to an AS that is not the rightful owner, the ASN Monitor will highlight the inconsistency even if a valid record exists.

In the screenshot above, the orange IRR entry indicates that although there are valid IRR records for the prefix, one of them points to a different origin, making it inconsistent. On the right side, the red RPKI entry highlights a similar situation: a record exists for the prefix, but it originates from an ASN that is not the rightful owner. These visual indicators make it easier to spot and act on conflicting information, even when at least one valid record is present.

Border Gateway Protocol (BGP) was never designed to be a searchable database or a tidy audit log. It’s a living conversation—messy, distributed, and refreshingly stateless.

ASN Monitor listens to that conversation 24×7 and turns yesterday’s fleeting updates into today’s actionable insight. Below is a tour of the seven workspaces that make it happen, using AS 52863 (UPX) for illustration.

1 · Main – “Am I healthy?”

Think of Main as your NOC-side dashboard:

Main is your at-a-glance health check for any ASN. It combines dashboards with 30-day histories for upstreams, downstreams, and peers so you can spot trend lines, drift, and anomalies in seconds. The AS Path chart shows how traffic actually reaches your ASN, highlighting connectivity to Tier-1 networks. Beneath the path, compact time-series charts track IPv4/IPv6 peer counts and prefixes (announced vs. originated), making growth, withdrawals, and maintenance effects immediately visible. 

A Recent & Critical Events panel keeps urgent issues front-and-center with one-click links to the full event log and path impact.

2 · Events – “Show me what changed, and when”

Events filters the firehose:

Events is your forensic logbook for BGP. A stacked timeline surfaces the busiest hours and most severe incidents—click anywhere to filter the table to that window. Quick toggles narrow by severity and category to find hijack, withdrawal, announcement, RPKI/IRR and  Upstream/Downstream changes, and free-text search finds the exact incident you need.

Every row opens a detailed view with the affected prefix/AS, RPKI state at that moment, a before/after AS-Path diff and other related metadata. It’s an always-on audit trail.

3 · Paths – “How attractive are my routes?”

BGP attraction is visual, so Paths is, too:

Paths turn observed AS-paths into a clean, directional map of route attraction. Tier-1s and major transits sit on the left, your origin AS on the right; Use the prefix filter to flip between “all prefixes” and a single /24 or /48—imbalances and asymmetries jump out immediately. Hover to highlight each node and its interconnectivities, then pivot to Announces for the full path list. In practice, this view answers three questions fast: who actually brings me traffic, how balanced my upstreams are, and whether a change shifted attraction toward the wrong provider.

4 · Announces – “Let’s open the hood”

Where Paths shows the forest, Announces lets you inspect every tree:

Announces is your per-prefix truth table. It lists every originating network and shows, across observed upstreams, how much of the path share each one carries. Use the prefix and v4/v6 filters to narrow the view. Click on the gauge to open the AS-Path Inspector and see all observed paths for that prefix—handy for quick verification or copy-out. 

Below the table, upstreams, downstreams, and peers are broken out with path counts and a compact treemap so you can gauge distribution at a glance. It’s the place to confirm propagation, spot imbalances, and trace exactly how a given route is being carried.

5 · Resources – “Is my paperwork in order?”

Your prefixes are only as good as their paperwork:

Resources audits the control-plane paperwork behind your prefixes. At the top, a compact summary shows current RPKI and IRR coverage so you can spot gaps quickly. The table below lists each originated prefix with last-seen time and clear status badges: RPKI Valid/Invalid/Not Found and IRR present/missing.

Click any row to open a prefix detail, where you can review the ROA/IRR evidence and see common failure reasons (e.g., wrong origin ASN, maxLength too short, expired ROA, or no object). Filters for IPv4/IPv6 and prefix search keep the view focused. It’s the fastest way to verify that policy artifacts match what you’re actually announcing—and to prioritize what needs fixing next.

6 · ASN Live – “What’s happening this second?”

When you need second-by-second telemetry, switch to ASN Live:

ASN Live streams announcements and withdrawals from multiple collectors in real time. A live grid shows prefixes against collectors; cells light up as updates arrive so you can see propagation (or the lack of it) at a glance.

Use quick filters to focus on a prefix, an upstream AS, or a time window, then pivot to Announces or Events for full context. It’s ideal for maintenance windows and incident response—helping you confirm changes, spot flapping, and catch routes that look “stuck” (announced but not refreshing or withdrawn).

7 · Settings – “My fleet, my rules”

Monitor any AS in the world and control your notification preferences:

Settings is the straightforward place to add or remove the ASNs you monitor and stay within plan limits. It also links to the Notification Center, where you choose which events trigger alerts (e.g., hijacks, visibility changes, new announcements, RPKI/ROA issues, upstream/downstream changes), how alerts are aggregated (real-time, daily, or weekly at a chosen UTC time), and where they’re delivered (Slack, email, or ServiceNow).

The tool that remembers what BGP forgets

ASN Monitor gives operators a reliable memory for an unreliable protocol. It unifies snapshots and real-time views so you can see what changed, why it changed, and how that change propagated—without wading through raw updates.

From Tier-1 attraction and per-prefix paths to IRR/RPKI posture and event forensics, the focus is practical insight you can act on quickly. Configure a few ASNs, set your notifications, and let the platform keep score in the background. BGP will keep forgetting; ASN Monitor won’t.