bgpreport

Network · data from 2026-11-12

AS9153 Burstfire Networks Ltd

Registry name: BURSTFIRE-EU Burstfire Networks Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9153, 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.
46.248.96.0/19 Valid RIR databaseRIPE 673 100% 67
82.136.0.0/18 Valid RIR databaseRIPE 673 100% 67
195.22.128.0/23 Valid RIR databaseRIPE 673 100% 67
2001:4088::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS9153: RIPE::AS-BURSTFIRE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS9153 isn't in the set, or no route object for AS9153 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS9153 in itNot covered
RIPE::AS-BURSTFIRE RIPElists itself further down6 member sets in no database: AS-DYFEDIT, AS-HAMLESH, AS-HSC, AS-KEWLIO-OFFSITE, AS-OCCAID … 139442,091 Yes 0

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

  • AS-SET: missing member6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS-DYFEDIT; no IRR database read has it.
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS-HAMLESH; no IRR database read has it.
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS-HSC; no IRR database read has it.
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS-KEWLIO-OFFSITE; no IRR database read has it.
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS-OCCAID; no IRR database read has it.
AS-SET: missing memberRIPE::AS-BURSTFIREAS-BURSTFIRE (RIPE) lists AS206754:AS-TRANSIT; no IRR database read has it.

Route objects not announced

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

82.136.8.0/22RIPEValid
193.164.13.0/24RIPENo ROA
2001:1a20::/32NTTCOMNo ROA
2001:40a0::/32NTTCOMNo ROA
2001:4bd0::/32NTTCOMNo 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.