Provider certification record
Yardi Systems, LLC
Listed- RMD number
- RMD0041584
- FRN
- 0038864013
- OCN
- 675H
Identity
- Legal business name
- Yardi Systems, LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 430 South Fairview Ave, Goleta CA 93117
- Filing contact
- Jason Yardi
Director · Telecommunications / yLine
jason.yardi@yardi.com
(805) 699-2040
430 South Fairview Ave Goleta CA 93117
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Parent company: Yardi Holdings, Inc. (Delaware). Subsidiary: Yardi Kube, Inc. (FRN 0026981340, separate RMD filer). Principals: Anant Yardi (Chief Executive Officer), Arnold Brier, Jason Yardi.Parent company: Yardi Holdings, Inc. (Delaware). Subsidiary: Yardi Kube, Inc. (FRN 0026981340, separate RMD filer). Principals: Anant Yardi (Chief Executive Officer), Arnold Brier, Jason Yardi.
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider Partial Overall Partial - Exemption rules
- Yardi Systems, LLC does not own or control the SIP network elements that insert a STIR/SHAKEN Identity header. Its calls are originated through wholesale carriers (Bandwidth, Twilio, Sinch) over their programmable voice platforms, and those carriers authenticate every call under 47 CFR 64.6301 with their own certificates. Yardi therefore lacks control of the network infrastructure needed to implement STIR/SHAKEN itself today. Yardi has registered FRN 0038864013, has been assigned Operating Company Number 675H by NECA (September 8, 2026), has submitted its FCC Form 499 filer registration, and will register with the STI-PA, obtain its own STI certificate, and authenticate its calls through a third-party signing service in accordance with the Eighth Report and Order, targeting the fourth quarter of 2026. This filing will be updated within 10 business days of that implementation. See the attached robocall mitigation program description.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- jason yardi
- Date
- 2026-09-09No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-09-09 | Field change | data.exemptionRules Yardi Systems, LLC does not own or control the SIP network elements that insert a STIR/SHAKEN Identity header. Its calls are originated through wholesale carriers (Bandwidth, Twilio, Sinch) over their programmable voice platforms, and those carriers authenticate every call under 47 CFR 64.6301 with their own certificates. Because Yardi lacks control of the network infrastructure needed to implement STIR/SHAKEN itself, it currently selects "No STIR/SHAKEN Implementation" as the Commission's RMD guidance directs for providers without such control. Yardi has registered FRN 0038864013, has requested an Operating Company Number from NECA, and will register with the STI-PA, obtain its own STI certificate, and authenticate its calls through a third-party signing service in accordance with the Eighth Report and Order, targeting the fourth quarter of 2026. This filing will be updated within 10 business days of that implementation. See the attached robocall mitigation program description.→Yardi Systems, LLC does not own or control the SIP network elements that insert a STIR/SHAKEN Identity header. Its calls are originated through wholesale carriers (Bandwidth, Twilio, Sinch) over their programmable voice platforms, and those carriers authenticate every call under 47 CFR 64.6301 with their own certificates. Yardi therefore lacks control of the network infrastructure needed to implement STIR/SHAKEN itself today. Yardi has registered FRN 0038864013, has been assigned Operating Company Number 675H by NECA (September 8, 2026), has submitted its FCC Form 499 filer registration, and will register with the STI-PA, obtain its own STI certificate, and authenticate its calls through a third-party signing service in accordance with the Eighth Report and Order, targeting the fourth quarter of 2026. This filing will be updated within 10 business days of that implementation. See the attached robocall mitigation program description. +1 more |
| 2026-09-07 | New | Initial certification filed and added to database. |