bgpreport

Network · data from 2026-11-12

AS36827 PINE BELT TELEPHONE

Registry name: PBTC-ARL - PINE BELT TELEPHONE CO, US · PeeringDB

2IPv4 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
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS36827, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36827, 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.

206.198.160.0/20 No ROA RIR databaseARIN, RADB 669 99% 68
208.66.184.0/21 No ROA RIR databaseARIN, RADB 669 99% 68
2604:e480::/32 No ROA RIR databaseARIN 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS36827: AS36827:AS-ALL. 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 (AS36827 isn't in the set, or no route object for AS36827 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 objectsAS36827 in itNot covered
AS36827:AS-ALL ARIN 115 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: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none206.198.160.0/20No ROA covers it. Add a ROA for AS36827, maxLength 20.669 of 673
ROA: none208.66.184.0/21No ROA covers it. Add a ROA for AS36827, maxLength 21.669 of 673
ROA: none2604:e480::/32No ROA covers it. Add a ROA for AS36827, maxLength 32.633 of 636

Route objects not announced

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

65.161.116.0/22RADBNo ROA
204.181.60.0/22RADBNo 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.