bgpreport

Network · data from 2026-11-12

AS219369 C2T

Registry name: C2T ConstructInTech Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS219369, 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.
195.10.233.0/24 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
87.199.140.0/24 Valid RIR databaseRIPE 673 100% 67
87.199.141.0/24 Valid RIR databaseRIPE 673 100% 67
87.199.140.0/23 Valid RIR databaseRIPE 672 100% 67
2a0b:9405::/33 Valid RIR databaseRIPE 636 100% 67
2a0b:9405:8000::/33 Valid RIR databaseRIPE 636 100% 67
2a0b:9405::/32 Valid RIR databaseRIPE 635 100% 67
2001:67c:b1c::/48 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS219369's PeeringDB record names no AS-SET.

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

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin195.10.233.0/24ROAs covering it name AS209505, not AS219369. If AS219369 should announce it, add a ROA for AS219369.1 of 673

Route objects not announced

Every route object with origin AS219369 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.