bgpreport

Network · data from 2026-11-12

AS14150 SSD - Societe de Services Dentaires (A.C.D.Q.) inc

Registry name: SSD - Societe de Services Dentaires (A.C.D.Q.) inc, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14150, 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.

192.154.140.0/24 Invalid: origin None 45 7%low visibility 30

AS-SET

AS14150 isn't in PeeringDB, where networks name their AS-SET.

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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin192.154.140.0/24ROAs covering it name AS10929, not AS14150. If AS14150 should announce it, add a ROA for AS14150.45 of 673
Route object: none192.154.140.0/24No route object for it. Add a route object with origin AS14150 in the RIR database for the space.45 of 673

Route objects not announced

Route objects with origin AS14150 whose prefix no peer sees AS14150 announce. Many are kept on purpose (backup routes, space announced only in some places).

65.125.240.0/24RADBNo ROA
198.51.93.0/24RADBNo ROA
198.51.94.0/24RADBNo ROA
205.168.177.0/24RADBNo ROA
205.169.170.0/24RADBNo ROA
205.169.222.0/24RADBNo ROA
207.78.104.0/24RADBNo ROA
216.38.32.0/19RADBNo ROA

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.