BGPMap

Snapshot gr9cgp3at9

Paths to 2a06:98c1:310b::/48

RPKI valid Prepend · 3 peers Global · RIPE RIS
Peers
350
Collectors
23
Unique paths
249
Prepends
3 peers
Origin
AS13335
Data time (UTC)

AS-path graphtoward 2a06:98c1:310b::/48

100%
  • Most Observed AS-PATH
  • Other observed edges
  • Origin AS
  • Prefix
Edge labels are peer counts. For legibility only edges seen by at least 10 peers are drawn; 273 rarer edges are hidden out of 249 unique paths. Nothing is discarded — the full upstream data stays in this snapshot.

AS prepends

3 of 350 peers · 3 variants

Some RIS peers see a longer path because a network repeats its own ASN (AS prepending). The graph collapses those repeats so the topology stays readable. The forms those peers actually reported are listed here, separate from the collapsed Most Observed AS-PATH.

  • AS46997 AS38008 ×2 AS13335

    Seen by 1 peer · RIS peer AS46997 at RRC24

    AS38008 ×2 (1 extra hop)

  • AS38008 ×2 AS13335

    Seen by 1 peer · RIS peer AS38008 at RRC25

    AS38008 ×2 (1 extra hop)

  • AS4601 ×2 AS13335

    Seen by 1 peer · RIS peer AS4601 at RRC20

    AS4601 ×2 (1 extra hop)

Evidence

Resource
2a06:98c1:310b::/48
Measured from
Global · RIPE RIS

Aggregated across every RIS peer that carries this prefix, so it reflects the global table rather than any single network's view.

Origin AS
Origin validation

A ROA covers this prefix and authorises this origin AS. Route Origin Validation is performed by the RIPE NCC RPKI Validator, which compares the observed origin AS against the prefix's published ROAs.

ROAs seen for this prefix: 1 matching, 0 for a different AS, 0 with a shorter maximum length.

Most Observed AS-PATH
AS24482 AS13335

Reported by 9 of 350 peers. This is the most frequent complete path in the data, not a “best path” — no such single path exists globally. Repeats are collapsed here; 3 peers saw an AS prepend, listed separately.

BGP communities
Flags
  • AS prepend observed on 3 of 350 peers
Citable snapshot

Snapshots are immutable. Running the same query again produces a new one with a fresh timestamp.