All Changes

Active filterschange type Field change ✕state Florida ✕Clear all
Events 26–31 of 31
25 50 100
Recent changes
Date/time (ET)ProviderRMDState / countryChange typeDetail / diff
2026-08-19 16:01Masters Telecom LLCRMD0002908FloridaField changedata.declarationDate 2026-02-24T00:00:00.000Z→2026-08-19T00:00:00.000Z
2026-08-18 11:23Smartbiz Telecom, LLCRMD0004849FloridaField changedata.signer Eduardo Borrero→Eduardo Borrerro +3 more
2026-08-18 10:31Premier IT Networks IncRMD0006815FloridaField changedata.signer Tzahi Zlikha President→Tzahi Zlikha +2 more
2026-08-17 09:22AnswerFirst CommunicationsRMD0006133FloridaField changedata.declarationDate 2026-02-19T00:00:00.000Z→2026-08-17T00:00:00.000Z
2026-08-14 12:37Aurora Trade, LLCRMD0005084FloridaField changedata.exemptionRules Aurora Trade LLC qualifies as an intermediate provider as defined in 47 C.F.R. § 64.1600(d). Under 47 C.F.R. § 64.6301(a), the STIR/SHAKEN implementation requirement applies to originating voice service providers. Aurora Trade LLC does not originate voice traffic, does not assign telephone numbers, and does not serve retail end users. Aurora operates solely as a wholesale intermediate provider carrying traffic received from originating voice service providers for delivery to international destinations. Accordingly, the STIR/SHAKEN implementation requirement does not apply to Aurora. Aurora complies with 47 C.F.R. § 64.6305(c) by maintaining a robocall mitigation program and responding fully and within 24 hours to traceback requests.→Aurora Trade LLC operates as a non-gateway intermediate provider and does not originate voice traffic, assign telephone numbers, or serve retail end users. Aurora operates solely as a wholesale intermediate provider carrying U.S.-originated traffic received from originating voice service providers for delivery to international destinations. Calls received directly by Aurora from its U.S. originating voice service provider customers are authenticated by those originating providers using the STIR/SHAKEN framework prior to receipt by Aurora. Accordingly, the caller identification information for these calls has already been authenticated when received by Aurora. Aurora does not authenticate or sign calls itself and has not implemented the STIR/SHAKEN authentication framework on any portion of its network. Aurora maintains a robocall mitigation program consistent with 47 C.F.R. § 64.6305(c), including reasonable steps to avoid carrying or processing illegal robocall traffic, and commits to respond fully and within 24 hours to traceback requests from the Commission, law enforcement, and the industry traceback consortium. +1 more
2026-08-13 19:33VNOXTEL LLCRMD0029853FloridaField changeroleVoice false→true +7 more
Showing events 26–31 of 31‹ Prev2Next › of 2