bgpreport

Network · data from 2026-11-12

AS206723 Carnsore Broadband Limited

Registry name: CARNSOREBROADBAND Carnsore Broadband Limited, IE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206723, 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.
149.5.32.0/24 No ROA Other IRR onlyRIPE-NONAUTH 664 99% 67
149.5.36.0/22 No ROA Other IRR onlyRIPE-NONAUTH 664 99% 67
185.58.16.0/22 No ROA RIR databaseRIPE 664 99% 68
185.178.68.0/22 No ROA RIR databaseRIPE 664 99% 68
2a0a:5880::/29 No ROA RIR databaseRIPE 621 98% 69
45.94.72.0/22 No ROA RIR databaseRIPE 109 16% 38

AS-SET

PeeringDB's irr_as_set for AS206723: AS206723. 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 (AS206723 isn't in the set, or no route object for AS206723 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 objectsAS206723 in itNot covered
AS206723 A single AS number, not a set: AS206723 (this network), 6 route objects.

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

  • ROA: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none149.5.32.0/24No ROA covers it. Add a ROA for AS206723, maxLength 24.664 of 673
Route object: RIR149.5.32.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.664 of 673
ROA: none149.5.36.0/22No ROA covers it. Add a ROA for AS206723, maxLength 22.664 of 673
Route object: RIR149.5.36.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.664 of 673
ROA: none185.58.16.0/22No ROA covers it. Add a ROA for AS206723, maxLength 22.664 of 673
ROA: none185.178.68.0/22No ROA covers it. Add a ROA for AS206723, maxLength 22.664 of 673
ROA: none2a0a:5880::/29No ROA covers it. Add a ROA for AS206723, maxLength 29.621 of 636
ROA: none45.94.72.0/22No ROA covers it. Add a ROA for AS206723, maxLength 22.109 of 673

Route objects not announced

Every route object with origin AS206723 is announced.

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.