bgpreport

Network · data from 2026-11-12

AS14773 Lancaster-Lebanon IU13 WAN

Registry name: LANLEB-IU13 - Lancaster Lebanon Intermediate Unit 13, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14773, 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.
2620:1d5:ff9::/48 Invalid: maxLength Nonecovered by 2620:1d5::/32 1 0%low visibility 1
2600:2501:f003::/48 No ROA Other IRR onlyRADB 634 100% 68
206.82.16.0/20 Valid RIR databaseARIN, RADB 671 100% 67
206.82.16.0/21 Valid RIR databaseARIN, RADB 671 100% 67
206.82.24.0/23 Valid RIR databaseARIN, RADB 671 100% 67
206.82.26.0/24 Valid RIR databaseARIN, RADB 671 100% 67
206.82.27.0/24 Valid RIR databaseARIN, RADB 671 100% 67
206.82.28.0/22 Valid RIR databaseARIN, RADB 671 100% 67
2620:1d5:ff0::/48 Valid RIR databaseARIN, RADB 635 100% 69
2620:1d5:ff1::/48 Valid RIR databaseARIN, RADB 635 100% 69
2620:1d5:ffa::/48 Valid RIR databaseARIN, RADB 635 100% 69
2620:1d5:ffc::/48 Valid RIR databaseARIN, RADB 635 100% 70
2620:1d5:ffe::/48 Valid RIR databaseARIN, RADB 635 100% 69
2620:1d5:fff::/48 Valid RIR databaseARIN, RADB 635 100% 69
2620:1d5::/40 Valid RIR databaseARIN, RADB 634 100% 69
2620:1d5:100::/40 Valid RIR databaseARIN, RADB 634 100% 69
2620:1d5:ffb::/48 Valid RIR databaseARIN, RADB 634 100% 69
2620:1d5::/32 Valid RIR databaseARIN, RADB 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS14773: ARIN::AS14773:AS-IU13WAN. 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 (AS14773 isn't in the set, or no route object for AS14773 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 objectsAS14773 in itNot covered
ARIN::AS14773:AS-IU13WAN ARIN 13367 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 5 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2620:1d5:ff9::/48ROA 2620:1d5::/32 AS14773 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2620:1d5:ff9::/48.1 of 636
Route object: none2620:1d5:ff9::/48No route object for it. A route object for 2620:1d5::/32 with origin AS14773 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14773 in the RIR database for the space.1 of 636
ROA: none2600:2501:f003::/48No ROA covers it. Add a ROA for AS14773, maxLength 48.634 of 636
Route object: RIR2600:2501:f003::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

173.246.253.128/27RADBNo 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.