Provider certification record
Bright Packet, Inc.
Listed- RMD number
- RMD0009730
- FRN
- 0021536735
- OCN
- 547J, 865J
Identity
- Legal business name
- Bright Packet, Inc.
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 11756 Artesia Blvd, Suite A, Artesia CA 90701
- Filing contact
- Jong Yeo
General Manager · main office
jong@brightpacket.com
(714) 705-4929
11756 Artesia Blvd Suite A Artesia CA 90701
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Jong Yeo – General Manager (Responsible Corporate Officer), No parent company, subsidiaries, or affiliates.
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Bright Packet, Inc. currently operates as a reseller of telecommunications services utilizing underlying carriers, including Verizon and AT&T. At present, the Company does not originate voice traffic over its own IP-based interconnections or directly authenticate outbound calls using the STIR/SHAKEN framework. All outbound voice traffic is currently delivered through underlying carriers, which are responsible for STIR/SHAKEN authentication and call attestation. The Company has obtained its STI-PA authorization, SPC token, and STIR/SHAKEN certificate. Implementation of STIR/SHAKEN authentication is pending completion of interconnection and outbound testing with its upstream carrier. Accordingly, the Company currently relies on its underlying carriers to perform STIR/SHAKEN authentication and robocall mitigation functions for outbound traffic.
Prior investigations / actions
- Description
- Bright Packet, Inc. was subject to an enforcement action by the Federal Communications Commission (FCC), including its Enforcement Bureau, in connection with its Robocall Mitigation Database (RMD) filing obligations. The action was initiated pursuant to an FCC Enforcement Bureau Order (DA 25-737) released on August 25, 2025. The FCC determined that the Company failed to comply with its obligations to maintain accurate and timely filings in the Robocall Mitigation Database, including the timely submission and maintenance of required updates. As a result, the Company was temporarily removed from the Robocall Mitigation Database. The Company subsequently completed all required corrective actions and submitted updated filings. On May 19, 2026, the FCC converted the Company's status from "Provisional Reinstatement" to "Full Reinstatement." The Company is currently listed in the FCC Robocall Mitigation Database with Full Reinstatement status. The Company has strengthened its internal compliance procedures, including enhanced regulatory oversight, updated filing controls, and improved KYC procedures, to ensure ongoing compliance with FCC requirements. The matter has been fully resolved, and the Company remains in good standing in the FCC Robocall Mitigation Database. The Company utilizes third-party upstream carriers, including Verizon and AT&T, to provide voice services. These underlying carriers perform robocall mitigation functions on behalf of the Company, including call analytics, traffic monitoring, and the blocking of suspected illegal or unwanted calls. The Company does not operate its own independent call analytics or call blocking platform and relies on these upstream providers to implement robocall mitigation measures. The Company also maintains internal policies to monitor traffic patterns and ensure continued compliance with applicable FCC robocall mitigation requirements. The Company relies on these upstream providers as part of its overall robocall mitigation strategy. The Company has obtained its STI-PA authorization, SPC token, and STIR/SHAKEN certificate. Implementation is currently pending completion of interconnection and outbound testing with its upstream carrier. Until implementation is complete, the Company will continue to rely on its upstream carriers to perform STIR/SHAKEN authentication and robocall mitigation functions.
Robocall mitigation plan
Declaration
- By
- Jong Yeo
- Date
- 2026-07-29No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-07-29 | New | Initial certification filed and added to database. |