asn.dev

Routing security

AS57307 BLAZE-NETWORKS Communicate Technology LTD

Unclassified RIPE

RPKI valid 100% 2 of 2 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 2 authorising this AS

Announcements

What this network originates

2 observed

Every prefix observed with AS57307 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
185.100.148.0/22RPKI validIRR53
188.227.240.0/21RPKI validIRR53

RPKI · ROAs

Route origin authorisations

2 ROAs

Signed statements by address holders that AS57307 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
185.100.148.0/22/24RIPENCC
188.227.240.0/21/24RIPENCC

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

2 objects · 0 not announced

Route objects naming AS57307 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.

PrefixSourceDescriptionMaintainerChangedRouting
185.100.148.0/22RIPE—UK-COMMUNICATE-1-MNT2025-12-15Announced
188.227.240.0/21RIPEBlaze Networks LtdUK-COMMUNICATE-1-MNT2025-12-15Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS57307 directly show who expects to carry it.

AS-setWhereRelationship
AS-C4LRIPELists AS57307 as a direct member
AS-COMMUNICATERIPELists AS57307 as a direct member

RPKI from rpki-client, validated 2026-11-02 13:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-02. Cross-check on bgp.he.net.