bgpreport

Network · data from 2026-11-12

AS198034 SENSOTELECOM

Registry name: SENSOTELECOM-AS VOIP Telecom SAS, FR · PeeringDB

8IPv4 routes 87.5% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS198034, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198034, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

185.153.28.0/22 No ROA RIR databaseRIPE 672 100% 66
185.153.30.0/23 Valid RIR databaseRIPE 673 100% 66
91.230.169.0/24 Valid RIR databaseRIPE 672 100% 66
185.153.28.0/23 Valid RIR databaseRIPE 672 100% 66
217.194.80.0/23 Valid RIR databaseRIPE 672 100% 66
217.194.82.0/24 Valid RIR databaseRIPE 672 100% 66
217.194.95.0/24 Valid RIR databaseRIPE 672 100% 66
45.10.44.0/24 Valid RIR databaseRIPE 671 100% 66
2a12:9240::/32 Valid RIR databaseRIPE 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS198034: AS198034. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS198034 isn't in the set, or no route object for AS198034 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS198034 in itNot covered
AS198034 A single AS number, not a set: AS198034 (this network), 9 route objects.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none185.153.28.0/22No ROA covers it. Add a ROA for AS198034, maxLength 22.672 of 673

Route objects not announced

Every route object with origin AS198034 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.