Network · data from 2026-11-12

AS199519 THATGUYJACK

Registry name: THATGUYJACK-NET Jack Brierley, GB · PeeringDB

0IPv4 routes

9IPv6 routes 100.0% RPKI valid · 88.9% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS199519, seen from no peer

Announced routes

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


2a12:bec0:21a::/48	Valid	Nonecovered by 2a12:bec0:210::/44	633 100%	67
2a12:bec0:21f::/48	Valid	RIR databaseRIPE	634 100%	69
2a12:bec0:210::/48	Valid	RIR databaseRIPE	633 100%	67
2a12:bec0:211::/48	Valid	RIR databaseRIPE	633 100%	67
2a12:bec0:212::/48	Valid	RIR databaseRIPE	633 100%	67
2a12:bec0:213::/48	Valid	RIR databaseRIPE	633 100%	67
2a12:bec0:214::/48	Valid	RIR databaseRIPE	632 99%	67
2a12:bec0:218::/48	Valid	RIR databaseRIPE	632 99%	67
2a12:bec0:21d::/48	Valid	RIR databaseRIPE	631 99%	67

AS-SET

PeeringDB's irr_as_set for AS199519: AS199519:AS-CUST. 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 (AS199519 isn't in the set, or no route object for AS199519 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.

Name	Database	ASNs	Sets	Route objects	AS199519 in it	Not covered
AS199519:AS-CUST	RIPE	2	1	9	Yes	0

Name

Database

ASNs

Sets

Route objects

AS199519 in it

Not covered

AS199519:AS-CUST

RIPE

Yes

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

Route object: none1
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a12:bec0:21a::/48	No route object for it. A route object for 2a12:bec0:210::/44 with origin AS199519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199519 in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a12:bec0:21a::/48

No route object for it. A route object for 2a12:bec0:210::/44 with origin AS199519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199519 in the RIR database for the space.

633 of 636

Route objects not announced

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


2a12:bec0:210::/44	RIPE	Valid

2a12:bec0:210::/44

RIPE

Valid

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.